Malicious code in amplitude-experiment (npm)
Description
The npm package [email protected] contains malicious code delivered via a dependency that points to an external URL instead of a proper registry version. Installing this package results in arbitrary code execution through lifecycle scripts from the fetched tarball. The package itself is a stub, with the manifest line acting as the delivery mechanism for the malicious payload. Any system with this package installed should be considered fully compromised, and all secrets and keys on that system must be rotated immediately from a different machine.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The amplitude-experiment package at version 55.0.0 declares a dependency with the same name pointing to a non-registry HTTPS URL (https://repo.securityctrl.com/amplitude-experiment). During npm install, this URL is fetched without version pinning or integrity checks, allowing arbitrary code execution via lifecycle scripts in the fetched tarball. The legitimate amplitude-experiment package is an inert stub, making the dependency declaration the primary attack vector. This setup resembles a dependency confusion attack, leveraging an implausibly high version number to supersede legitimate versions. The compromise is severe enough that any system with this package installed should be treated as fully compromised.
Potential Impact
Systems with [email protected] installed are fully compromised due to arbitrary code execution from malicious lifecycle scripts. Attackers may gain complete control over the affected system, potentially accessing all stored secrets and keys. Removal of the package alone does not guarantee eradication of the malicious presence, necessitating secret/key rotation from a secure environment.
Mitigation Recommendations
Remove the [email protected] package immediately from all affected systems. Rotate all secrets and keys stored on compromised machines from a separate, secure system. Since the package installs malicious code via an external URL without integrity checks, avoid installing packages that declare dependencies from untrusted URLs. Monitor for any signs of persistent compromise and consider rebuilding affected systems to ensure full remediation. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-15496
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a92f7e3acd9273b49e75d22
Added to database: 08/29/2026, 15:16:51 UTC
Last enriched: 09/09/2026, 20:23:53 UTC
Last updated: 10/04/2026, 04:25:46 UTC
Views: 27
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.