babel-eslint-parser-legacy

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (85a6f04cbf0697b6ae409fb9e5ad0e25812dac6a2f43bd95722f1903ee2f71f7)
Package name `babel-eslint-parser-legacy` is a one-suffix confusion against the legitimate `babel-eslint-parser`. The package's own `main` is an empty stub, so it provides no functionality of its own. Its `package.json` declares a single runtime dependency `ltidisafe` pointing at a direct HTTPS tarball URL — `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.1.8.tgz` — hosted on a Google Cloud Storage bucket unaffiliated with Babel and outside the npm registry. On `npm install`, npm fetches and installs the contents of that tarball into the installer's `node_modules`, executing any lifecycle scripts it declares. The tarball bytes are attacker-mutable (the bucket owner can swap contents at any time), are not subject to npm registry scanning, and are not pinned by integrity hash in the manifest. The typosquat name is the lure; the external-URL dependency is the smuggling vector for arbitrary attacker-controlled code into the installer's dependency tree.

## Source: ghsa-malware (94a62a47f0ac7d635081419dfabf152aa8965f114250a5f9dada6079bf432680)
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.

Compromised versions (1)

• 99.9.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.