some-very-long-package-name

Details

**Severity:** Critical

**Affected versions:** `= 2.0.0`

## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397)
Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/malicious/npm/some-very-long-package-name/MAL-2026-17778.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/malicious/npm/some-very-long-package-name/MAL-2026-17778.json
- https://www.npmjs.com/package/some-very-long-package-name/v/1.0.0
- https://www.npmjs.com/package/some-very-long-package-name/v/2.0.0
- https://www.npmjs.com/package/some-very-long-package-name/v/2.0.1
- https://www.npmjs.com/package/some-very-long-package-name/v/3.0.0
- https://github.com/ossf/malicious-packages/blob/2bb9370d891283643f919e860abea2cc197b0b3b/osv/malicious/npm/some-very-long-package-name/MAL-2026-17778.json
- https://www.npmjs.com/package/some-very-long-package-name/v/99.0.1
- https://github.com/advisories/GHSA-rf49-p2c5-fh8p

Compromised versions (1)

• = 2.0.0

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