Malware in @johntaohunter/forge-jsx
Malware was discovered in the npm package @johntaohunter/forge-jsx. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @johntaohunter/forge-jsx
A malicious package named @johntaohunter/forge-jsx was published to npm and contained malware. According to the GitHub Security Advisory (GHSA-v9x2-2qjf-q7qp), any system that installed or ran this package should be treated as fully compromised.\n\nThe advisory recommends that all secrets, keys, and credentials stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full system compromise may have occurred, meaning removal of the package alone may not eliminate all malicious software that was installed.\n\nAffected users should assume complete loss of confidentiality and integrity on any system where this package was present.
Indicators of compromise
- Packages
- @johntaohunter/forge-jsx
Remediation
- Immediately remove the @johntaohunter/forge-jsx package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Assume full system compromise and conduct forensic analysis on affected machines
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-v9x2-2qjf-q7qp · GitHub Advisory Database
Cite this entry
"Malware in @johntaohunter/forge-jsx." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-johntaohunter-forge-jsx-1q0cz0
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 chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in @finxsecdemo/utils (npm)
The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in @bowozzz/baileys
The npm package @bowozzz/baileys contained 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
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package