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

3layerdipstacksn9zenpm

3layerdipstacksn9ze is a confirmed malicious npm package (MAL-2026-14921) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 3layerdipstacksn9ze (npm)

MAL-2026-14921
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall 3layerdipstacksn9ze

What this malware does

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

217139f17daa8d583a617a40cc2bbe6942e4d8e8591e00b6ea14ccce5678f1da

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for 3layerdipstacksn9ze (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 3layerdipstacksn9ze across your stack and pipelines.

  2. If you installed it — respond

    Remove 3layerdipstacksn9ze from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If 3layerdipstacksn9ze was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks 3layerdipstacksn9ze before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. 3layerdipstacksn9ze on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jhw5-j257-gx3w

References

Detect & block this

O3 blocks 3layerdipstacksn9ze-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

3layerdipstacksn9ze (npm) malicious package — MAL-2026-14921 | O3 Security