Malware in bnpl-blocks-atom-bnpl-dangerously-html
Malware was discovered in the npm package bnpl-blocks-atom-bnpl-dangerously-html. 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
- bnpl-blocks-atom-bnpl-dangerously-html
A malware incident was identified in the npm package bnpl-blocks-atom-bnpl-dangerously-html. According to the GitHub Advisory (GHSA-h385-qp77-g974), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately 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 the potential for full system compromise.\n\nUsers should treat any system that has run this package as potentially containing persistent malware and take appropriate containment and recovery measures.
Indicators of compromise
- Packages
- bnpl-blocks-atom-bnpl-dangerously-html
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the bnpl-blocks-atom-bnpl-dangerously-html package from all affected systems
- Perform a full security audit and malware scan on any system that had this package installed
- Consider the affected system(s) as potentially compromised and plan for full rebuild or forensic analysis
- Review access logs and audit trails for any unauthorized activity on affected systems
- Notify any services or systems that may have been accessed from the compromised computer
Sources
- GitHub Advisory GHSA-h385-qp77-g974 · GitHub Advisory Database
Cite this entry
"Malware in bnpl-blocks-atom-bnpl-dangerously-html." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-bnpl-blocks-atom-bnpl-dangerously-html-1xrhdc
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in @zizie071/libsignal-node
The npm package @zizie071/libsignal-node contains malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malware in @siwatfa/yorn
Malware was discovered in the npm package @siwatfa/yorn. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package - resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package