Malware in hjs-biginteger
Malware was discovered in the npm package hjs-biginteger, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- hjs-biginteger
A critical malware incident was identified in the npm package hjs-biginteger. According to the GitHub Advisory (GHSA-375r-m6vq-m5qp), any computer that has 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 initial compromise, given that the attacker may have gained full control of the system.\n\nThe incident was published on 2026-07-06 via the GitHub Advisory database.
Indicators of compromise
- Packages
- hjs-biginteger
Remediation
- Immediately rotate all secrets and keys stored on affected computers from a different, uncompromised system
- Remove the hjs-biginteger package from all systems
- Conduct a full security audit and forensic analysis of any system that had the package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider the affected system fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-375r-m6vq-m5qp · GitHub Advisory Database
Cite this entry
"Malware in hjs-biginteger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-hjs-biginteger-1r4qw9
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. 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