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

another-very-long-namenpm

Advisory published Updated

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

Malicious code in another-very-long-name (npm)

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

What this malware does

[email protected] ships a beacon.cjs that is invoked both from the declared postinstall lifecycle script and from the module's require()-time entry (index.js). On execution it collects host identifiers — hostname, install path, process.cwd(), process.version, OS metadata, and the package name — and POSTs them as JSON to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The package exposes no genuine functionality: index.js returns a Proxy whose get handler returns a no-op for every property so that bundlers consuming the package do not fail, and an author comment states that a build that completes and calls back is cleaner evidence. The destination is a bare-IP HTTP endpoint with no first-party relationship to any declared publisher, and the stub-plus-beacon shape is consistent with a dependency-confusion reconnaissance probe rather than a compatibility shim.

Malicious versions

4 flagged
1.0.11.1.02.0.02.0.1

Indicators of compromise (SHA-256)

6988ed51b76af3ebc9669995197300dc5fc6033d22ddae47452d29eb1805d8b8
eea9e3cf3d973c07d09048435d4ddc496574ce222d650c228b1400d866ea3ccf
6aca6f0008885dfc94cb075eafd3046583b8145832841e9b6bdcdcd7d3f6b677
91f6c27f7806ad8e28214d0f55858f9cc7255639414dc1425ff5301919df5aff

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for another-very-long-name (4 malicious versions).

  2. If you installed it — respond

    another-very-long-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 another-very-long-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. another-very-long-name on npm has been identified as a malicious package (versions 1.0.1, 1.1.0, 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021408IN-MAL-2026-021414IN-MAL-2026-021415IN-MAL-2026-021411

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks another-very-long-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.

Explore

another-very-long-name (npm) malicious package — MAL-2026-17767 | O3 Security