Malicious code in some-very-long-package-name (npm)
Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.
osv · MAL-2026-17778
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (58c08ea2abb307f6ecb9a1896fcc3980e9a1eaf8b29044db67cd985654e1db16) The package is a stub whose main module exports a Proxy that returns a no-op for every property access, providing none of the functionality implied by the package name or its 'compatibility shim' description. Its only real behavior is beacon.cjs, which collects host and install identifiers (hostname, install path, process.cwd(), process.version, package name/user-agent) and POSTs them to the hardcoded bare-IP HTTP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both automatically at install time via scripts.postinstall and again when the module is loaded via require(), because index.js invokes beacon.fire(). The shape — stub module, hardcoded non-DNS bare-IP C2 over plain HTTP, collection of installer host identifiers at install and require time — is consistent with a dependency-confusion / internal-name-squat reconnaissance beacon reporting successful installation inside private build environments.
- Source published
- 11 Oct 2026 13:54:49 UTC
- Source modified
- 11 Oct 2026 17:30:47 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.