Malicious code in corporate-front-vue (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d26a235f294aacb3800465f89db0f33ecb54f09da450ee98543f8b039249fc12) [email protected] is a near-empty shim (index.js exports an empty object) whose only meaningful content is a tarball-URL dependency declared in package.json: `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.7.tgz"`. On `npm install`, npm fetches and installs that tarball directly from an arbitrary Google Cloud Storage bucket — bypassing npm registry review — and executes whatever lifecycle scripts and code it contains on the installer's machine. The package metadata reinforces the dependency-confusion shape: version 99.9.1 (a classic high-overshoot designed to outrank an internal-registry package of the same name), empty description, empty author, default ISC license. The path segment `depenconf` in the tarball URL further matches the dependency-confusion pattern. The registry-visible package exists solely as a loader for non-registry, attacker-controlled bytes. ## Source: ghsa-malware (d7afd5758856a97831432ae76a0fd98a9cd41a5065ec890f8f922ccb98967476) 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
The [email protected] package is a malicious npm package that functions primarily as a loader for an attacker-controlled tarball hosted on Google Cloud Storage. This tarball is fetched and installed during npm install, bypassing npm registry security controls. The package metadata is crafted to facilitate dependency confusion attacks, using a high version number to outrank legitimate internal packages and a URL path segment indicative of dependency confusion. The package exports an empty object but triggers execution of arbitrary code via lifecycle scripts from the external tarball, potentially compromising the host system entirely.
Potential Impact
Any system that installs or runs [email protected] 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, it can establish persistent backdoors or other malware. Simply removing the package does not ensure removal of all malicious artifacts, necessitating comprehensive incident response and secret rotation.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove [email protected] from all systems. All secrets and keys on affected machines should be rotated from a secure, uncompromised environment. Monitor for any signs of compromise and conduct thorough forensic analysis to identify and eradicate any persistent malicious code. Avoid installing packages from untrusted sources or those that depend on external tarballs outside the npm registry.
Malicious code in corporate-front-vue (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d26a235f294aacb3800465f89db0f33ecb54f09da450ee98543f8b039249fc12) [email protected] is a near-empty shim (index.js exports an empty object) whose only meaningful content is a tarball-URL dependency declared in package.json: `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.7.tgz"`. On `npm install`, npm fetches and installs that tarball directly from an arbitrary Google Cloud Storage bucket — bypassing npm registry review — and executes whatever lifecycle scripts and code it contains on the installer's machine. The package metadata reinforces the dependency-confusion shape: version 99.9.1 (a classic high-overshoot designed to outrank an internal-registry package of the same name), empty description, empty author, default ISC license. The path segment `depenconf` in the tarball URL further matches the dependency-confusion pattern. The registry-visible package exists solely as a loader for non-registry, attacker-controlled bytes. ## Source: ghsa-malware (d7afd5758856a97831432ae76a0fd98a9cd41a5065ec890f8f922ccb98967476) 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
The [email protected] package is a malicious npm package that functions primarily as a loader for an attacker-controlled tarball hosted on Google Cloud Storage. This tarball is fetched and installed during npm install, bypassing npm registry security controls. The package metadata is crafted to facilitate dependency confusion attacks, using a high version number to outrank legitimate internal packages and a URL path segment indicative of dependency confusion. The package exports an empty object but triggers execution of arbitrary code via lifecycle scripts from the external tarball, potentially compromising the host system entirely.
Potential Impact
Any system that installs or runs [email protected] 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, it can establish persistent backdoors or other malware. Simply removing the package does not ensure removal of all malicious artifacts, necessitating comprehensive incident response and secret rotation.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove [email protected] from all systems. All secrets and keys on affected machines should be rotated from a secure, uncompromised environment. Monitor for any signs of compromise and conduct thorough forensic analysis to identify and eradicate any persistent malicious code. Avoid installing packages from untrusted sources or those that depend on external tarballs outside the npm registry.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5438
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-j2pq-r63w-52j5"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a520ed368715ace43901bbc
Added to database: 07/11/2026, 09:37:23 UTC
Last enriched: 07/11/2026, 10:01:19 UTC
Last updated: 07/27/2026, 02:31:10 UTC
Views: 9
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.