Malicious code in fund-portfolio (npm)
The npm package fund-portfolio version 999.9.12 was identified as malicious by the OpenSSF Package Analysis project. The malicious version communicates with a domain associated with malicious activity.
- Disclosed
- Last updated
- Blast radius
- All users of fund-portfolio version 999.9.12 and potentially earlier versions
- Ecosystems
- Attack vectors
- Affected entities
- fund-portfolio · 999.9.12
The OpenSSF Package Analysis project identified fund-portfolio version 999.9.12 on npm as containing malicious code. The package was flagged for communicating with a domain associated with malicious activity, indicating potential data exfiltration, command-and-control communication, or other malicious behavior.\n\nThis incident was discovered and reported through the OpenSSF's malicious-packages repository, which systematically analyzes packages for suspicious behavior and known indicators of compromise.\n\nUsers who have installed fund-portfolio version 999.9.12 should immediately remove the package and audit their systems for any unauthorized activity or data access.
Indicators of compromise
- Packages
- fund-portfolio@999.9.12
Remediation
- Immediately uninstall fund-portfolio version 999.9.12 from all affected systems
- Audit npm package.lock or yarn.lock files to identify all installations of the malicious version
- Review system logs and network traffic for any suspicious outbound connections to malicious domains
- Consider rotating any credentials or sensitive data that may have been exposed
- Update to a safe version of fund-portfolio if a legitimate version exists, or use an alternative package
- Monitor for any unauthorized access or activity on systems that had the malicious package installed
Sources
- GitHub Advisory GHSA-8qph-p7jr-c2xf · GitHub Advisory Database
Cite this entry
"Malicious code in fund-portfolio (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 23, 2026; last updated August 23, 2026. https://supplychainattack.org/incident/malicious-code-in-fund-portfolio-npm-1wkk79
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package