Supply chain · npm · High

Malicious npm Package 'fund-list-filter' Identified

Threat Engine Auto-Feed · data current as of 2026-08-23

A critical severity malicious package, 'fund-list-filter' version 999.9.12, has been identified in the npm ecosystem. This package communicates with a domain associated with malicious activity, posing a supply-chain risk to any systems that installed it. Immediate action is required to detect and remove this package.

  • Package: npm / fund-list-filter
  • Affected versions: = 999.9.12
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Malicious package

The npm package 'fund-list-filter' version 999.9.12 was identified as malicious by the OpenSSF Package Analysis project. The package's malicious nature stems from its communication with a domain known to be associated with malicious activity.

How the attack works

This is a malicious package attack, where a seemingly legitimate software component is designed to perform unauthorized or harmful actions. Upon installation and execution, the package initiates communication with an external, malicious domain, potentially exfiltrating data or receiving further instructions. This type of attack leverages the trust placed in package ecosystems and the automated dependency resolution in modern software development.

Who's exposed

Profiles most at risk

  • Development teams using the npm ecosystem
  • Organizations with CI/CD pipelines that pull unpinned or latest versions of npm packages
  • Any project that directly or indirectly depends on 'fund-list-filter' version 999.9.12

Conditions that increase exposure

  • Unpinned dependency versions in package.json (e.g., using '^' or '~' without a lockfile)
  • Lack of package-lock.json or yarn.lock files, allowing dynamic dependency resolution
  • Use of internal package mirrors that do not vet packages for known malicious activity
  • Automated builds that install dependencies without integrity checks

Blast-radius scenarios

  • If installed, the package could establish outbound communication to a malicious command-and-control server, potentially leading to data exfiltration or further compromise of the build environment or runtime system.
  • An attacker could gain initial access to development environments or production systems where the package is executed, expanding the blast radius to sensitive data or infrastructure.
  • Compromised systems could be used as a pivot point for lateral movement within an organization's network.

What to do (defensive)

Detect

  • Scan all project dependencies for 'fund-list-filter' version 999.9.12 using software composition analysis (SCA) tools.
  • Review package-lock.json or yarn.lock files for the presence of the malicious package.
  • Monitor network traffic for outbound connections from build systems or applications to known malicious domains, specifically those associated with this package.
  • Audit npm install logs and CI/CD pipeline logs for installation of the affected version.

Contain

  • Immediately quarantine or isolate any systems identified as having installed 'fund-list-filter' version 999.9.12.
  • Block network communication to the malicious domain identified by the OpenSSF Package Analysis project.
  • Prevent further installations of the specific malicious version by configuring package registries or firewalls.

Remediate

  • Remove 'fund-list-filter' version 999.9.12 from all affected projects and environments.
  • Update package dependencies to known safe versions or remove the dependency if it is not critical.
  • Rebuild affected applications and redeploy to clean environments.
  • Rotate credentials and API keys that may have been exposed on compromised build systems or runtime environments.
  • Implement strict dependency pinning and use lockfiles (package-lock.json, yarn.lock) to ensure reproducible builds and prevent unexpected dependency updates.

Frontier verdict — High

Prioritize immediate detection and removal of 'fund-list-filter' version 999.9.12 due to its critical severity and malicious network communication.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.