Malicious code in apex-trading (npm)
The npm package apex-trading was identified as malicious by both Amazon Inspector and the OpenSSF Package Analysis project. Version 1.0.4 executes commands associated with malicious behavior.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed apex-trading, particularly version 1.0.4
- Ecosystems
- Attack vectors
- Affected entities
- apex-trading · 1.0.4
The npm package apex-trading was flagged as malicious by multiple security sources. Amazon Inspector and the OpenSSF Package Analysis project independently identified the package as containing malicious code.\n\nVersion 1.0.4 of apex-trading was specifically analyzed and found to execute one or more commands associated with malicious behavior. The malicious activity was detected through automated package analysis conducted by the OpenSSF.\n\nThe package has been cataloged in the OpenSSF's malicious packages repository (MAL-2026-3817), indicating it was confirmed as a supply chain attack vector.
Indicators of compromise
- Packages
- apex-trading@1.0.4
Remediation
- Remove apex-trading from all projects immediately
- Audit any systems where apex-trading was installed for signs of compromise
- Review package.json and lock files for any dependencies on apex-trading
- Consider rotating credentials and secrets on affected systems
- Monitor for any suspicious activity on systems that may have executed the malicious package
Sources
- GitHub Advisory GHSA-rc69-pqv3-hw66 · GitHub Advisory Database
Cite this entry
"Malicious code in apex-trading (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 28, 2026. https://supplychainattack.org/incident/malicious-code-in-apex-trading-npm-17d81k
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 @vaultflow/create-flow
Malware discovered in the npm package @vaultflow/create-flow. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in @vaultflow/update-flow
Malware was discovered in the npm package @vaultflow/update-flow. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.
npmCompromised package - resolvedcritical
Malicious code in tempo-components (npm)
The npm package tempo-components contained malicious code (poc.js) that collected host metadata and identity information and exfiltrated it to an external endpoint. The package performed system reconnaissance by capturing hostname, platform, and user identity before transmitting the data via HTTPS.
npmCompromised package - containedcritical
Malicious code in @antv/g-webgl-compute (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including @antv/g-webgl-compute, as part of the "Mini Shai-Hulud" supply chain attack campaign. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit