Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

some-very-long-package-namenpm

Advisory published Updated

some-very-long-package-name is a confirmed malicious npm package (MAL-2026-17778) that opens a backdoor for remote access (malicious versions 1.0.0, 2.0.0, 2.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in some-very-long-package-name (npm)

MAL-2026-17778
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall some-very-long-package-name

What this malware does

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.

Malicious versions

5 flagged
1.0.02.0.02.0.13.0.099.0.1

Indicators of compromise (SHA-256)

1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397
5ff2c62f8ba9aff2b9a3d40aabc54116bf6522b9e048c362999642dcfcbe8f27
60ddbb54f68f4722fff212d66ceabc2675695a0f899749b34980f6176126024e
f81246a5c2ed84f640a9ab381bb84122a2f0c75fce7cb992dafcdc6b6736fcab
58c08ea2abb307f6ecb9a1896fcc3980e9a1eaf8b29044db67cd985654e1db16

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for some-very-long-package-name (5 malicious versions).

  2. If you installed it — respond

    some-very-long-package-name establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If some-very-long-package-name was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. some-very-long-package-name on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 2.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021407IN-MAL-2026-021437IN-MAL-2026-021438IN-MAL-2026-021435IN-MAL-2026-021449

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks some-very-long-package-name-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
some-very-long-package-name (npm) malicious package — MAL-2026-17778 | O3 Security