Malware in dolyame-boxy-independent-bnpl-open-api
Malware discovered in the npm package dolyame-boxy-independent-bnpl-open-api. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- dolyame-boxy-independent-bnpl-open-api
A malware incident has been identified in the npm package dolyame-boxy-independent-bnpl-open-api. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given that the outside entity may have gained full control of the system.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- dolyame-boxy-independent-bnpl-open-api
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the dolyame-boxy-independent-bnpl-open-api package from all affected systems
- Assume full system compromise and conduct thorough security audit
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review system logs for any suspicious activity since package installation
Sources
- GitHub Advisory GHSA-8hvr-g6xj-288x · GitHub Advisory Database
Cite this entry
"Malware in dolyame-boxy-independent-bnpl-open-api." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-dolyame-boxy-independent-bnpl-open-api-1knmgk
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