Malware in aone-sandbox
The npm package aone-sandbox contained malware that compromised any system where it was installed or executed. The package granted outside entities full control of affected computers.
- Disclosed
- Last updated
- Blast radius
- Any system with aone-sandbox installed or running
- Ecosystems
- Attack vectors
- Affected entities
- aone-sandboxnpm package containing malware
The npm package aone-sandbox was found to contain malware. Installation or execution of this package resulted in full system compromise, granting outside entities complete control over the affected computer.
Any system with aone-sandbox installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected computers must be rotated immediately from a different, uncompromised system.
While the malicious package should be removed, complete remediation cannot be guaranteed due to the level of access granted to the attacker. Additional malicious software may persist on the system even after package removal.
This incident was disclosed via GitHub Advisory GHSA-mv5v-q5f3-gf7h on 2026-07-28.
Indicators of compromise
- Packages
- aone-sandbox
Remediation
- Immediately remove the aone-sandbox package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Assume full system compromise and consider rebuilding affected systems from clean media
- Audit system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any persistence mechanisms or additional malware that may have been installed
Sources
- GitHub Advisory GHSA-mv5v-q5f3-gf7h · GitHub Advisory Database
Cite this entry
"Malware in aone-sandbox." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 28, 2026; last updated July 28, 2026. https://supplychainattack.org/incident/malware-in-aone-sandbox-jl4bf4
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package