Malicious code in npm-extension (npm)
Description
The npm-extension package version 45.0.0 contains malicious code delivered via a dependency declared as a bare HTTPS URL rather than a standard registry version. This causes npm to fetch and execute unverified third-party code during installation, leading to potential full system compromise. The package's own code is inert, but the fetched code runs with installer privileges. Systems with this package installed should be considered compromised, and all secrets and keys must be rotated. Removal of the package alone may not fully remediate the infection.
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 npm-extension package version 45.0.0 declares a dependency using a bare HTTPS URL (https://repo.securityctrl.com/npm-extension) instead of a version range from the npm registry. This forces npm to fetch a tarball from an off-registry host and execute any lifecycle scripts contained therein without integrity verification. The package's own index.js is inert, meaning the malicious payload is entirely delivered through the fetched third-party code. This dependency-confusion style attack results in arbitrary code execution on machines installing the package, potentially leading to full system compromise.
Potential Impact
Any system that installs or runs the npm-extension package version 45.0.0 is at risk of full compromise. Attackers may gain complete control over the affected machine, potentially accessing all stored secrets and keys. Because the malicious code executes during installation with no integrity checks, the system's security is severely undermined. Simply removing the package does not guarantee removal of all malicious artifacts or backdoors introduced by the attacker.
Mitigation Recommendations
Immediate removal of the npm-extension package version 45.0.0 is recommended. All secrets and keys on affected systems should be rotated from a separate, trusted machine. Due to the high risk of full compromise, a full system forensic analysis and potential rebuild may be necessary. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates or official fixes. Avoid installing packages that declare dependencies via bare HTTPS URLs from untrusted sources.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-15515
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a92f7e3acd9273b49e75d18
Added to database: 08/29/2026, 15:16:51 UTC
Last enriched: 09/09/2026, 20:24:16 UTC
Last updated: 10/02/2026, 11:02:12 UTC
Views: 21
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.