Malicious code in localization-lib (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bf143361939feffe7099c14acc7cf41a401681481e932e15d6054dde49e88f94) [email protected] is an empty shell package: `index.js` is `module.exports = {}` and `package.json` has no description or author. Its `dependencies` declares `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.0.1.tgz"`, resolving a transitive dependency directly from a third-party Google Cloud Storage bucket rather than the npm registry. On `npm install`, npm fetches and installs that opaque tarball and executes any lifecycle hooks it declares on the installer's machine. The version `99.9.1` is the canonical outranking-version pattern used in dependency-confusion attacks to override a legitimate internally-named package, and the URL path literally contains the token `depenconf`. The package has no functional purpose other than smuggling this off-registry dependency into the installer's environment. ## Source: ghsa-malware (401dface4dee0f5b93603c52d947b3e856983c806dca6453edc9efef6afa482b) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
[email protected] is a malicious npm package that acts as a dependency confusion attack vector by declaring a dependency on an off-registry tarball hosted at a third-party Google Cloud Storage URL containing the token 'depenconf'. The package itself is an empty shell with no functional code, but its installation triggers npm to download and execute code from an untrusted source. This can lead to full system compromise. The version number 99.9.1 is a canonical outranking version used to override legitimate internal packages. The package is designed solely to smuggle malicious code into the environment of the user installing it.
Potential Impact
Any system that installs [email protected] is at risk of full compromise. The malicious package can execute arbitrary code during installation, potentially giving attackers complete control over the affected system. All secrets and keys stored on the compromised system should be considered exposed and must be rotated from a secure environment. Simply removing the package does not guarantee removal of all malicious artifacts or backdoors introduced by the package.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove [email protected] from all environments. Treat any system with this package installed as fully compromised. Rotate all secrets and credentials that were stored or accessible on the affected systems from a separate, secure machine. Conduct a thorough incident response to identify and remediate any persistent malicious software or backdoors. Avoid installing packages from untrusted or off-registry sources, and audit dependencies for suspicious URLs or version numbers indicative of dependency confusion attacks.
Malicious code in localization-lib (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bf143361939feffe7099c14acc7cf41a401681481e932e15d6054dde49e88f94) [email protected] is an empty shell package: `index.js` is `module.exports = {}` and `package.json` has no description or author. Its `dependencies` declares `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.0.1.tgz"`, resolving a transitive dependency directly from a third-party Google Cloud Storage bucket rather than the npm registry. On `npm install`, npm fetches and installs that opaque tarball and executes any lifecycle hooks it declares on the installer's machine. The version `99.9.1` is the canonical outranking-version pattern used in dependency-confusion attacks to override a legitimate internally-named package, and the URL path literally contains the token `depenconf`. The package has no functional purpose other than smuggling this off-registry dependency into the installer's environment. ## Source: ghsa-malware (401dface4dee0f5b93603c52d947b3e856983c806dca6453edc9efef6afa482b) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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
[email protected] is a malicious npm package that acts as a dependency confusion attack vector by declaring a dependency on an off-registry tarball hosted at a third-party Google Cloud Storage URL containing the token 'depenconf'. The package itself is an empty shell with no functional code, but its installation triggers npm to download and execute code from an untrusted source. This can lead to full system compromise. The version number 99.9.1 is a canonical outranking version used to override legitimate internal packages. The package is designed solely to smuggle malicious code into the environment of the user installing it.
Potential Impact
Any system that installs [email protected] is at risk of full compromise. The malicious package can execute arbitrary code during installation, potentially giving attackers complete control over the affected system. All secrets and keys stored on the compromised system should be considered exposed and must be rotated from a secure environment. Simply removing the package does not guarantee removal of all malicious artifacts or backdoors introduced by the package.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove [email protected] from all environments. Treat any system with this package installed as fully compromised. Rotate all secrets and credentials that were stored or accessible on the affected systems from a separate, secure machine. Conduct a thorough incident response to identify and remediate any persistent malicious software or backdoors. Avoid installing packages from untrusted or off-registry sources, and audit dependencies for suspicious URLs or version numbers indicative of dependency confusion attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5447
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-2qhv-h564-p9rm"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a520ed368715ace43901a0e
Added to database: 07/11/2026, 09:37:23 UTC
Last enriched: 07/11/2026, 10:00:32 UTC
Last updated: 07/29/2026, 07:54:36 UTC
Views: 15
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.