Malware in @apexcraft/nano-key
Malware was discovered in the npm package @apexcraft/nano-key. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @apexcraft/nano-key
A critical malware incident was identified in the npm package @apexcraft/nano-key. According to the GitHub Advisory (GHSA-8x7w-vjr2-7q4m), any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory recommends that all secrets and cryptographic keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that because the malware may have granted full control of the system to an external entity, removal of the package alone cannot guarantee complete remediation of all malicious software that may have been installed.\n\nThis represents a critical supply chain compromise affecting the npm ecosystem.
Indicators of compromise
- Packages
- @apexcraft/nano-key
Remediation
- Immediately isolate any system that has installed or run @apexcraft/nano-key from the network
- Rotate all secrets, API keys, credentials, and cryptographic keys from a different, uncompromised computer
- Remove the @apexcraft/nano-key package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the system handles sensitive data or credentials
Sources
- GitHub Advisory GHSA-8x7w-vjr2-7q4m · GitHub Advisory Database
Cite this entry
"Malware in @apexcraft/nano-key." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-apexcraft-nano-key-1rirtb
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package