Which versions of 3layerdipstackl21ibf are malicious?

The following npm versions of 3layerdipstackl21ibf are flagged malicious: 0.1.4. Treat any of these as compromised.

How do I remediate 3layerdipstackl21ibf if I installed it?

Remove 3layerdipstackl21ibf 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.

I already installed 3layerdipstackl21ibf — how do I know if it already compromised me?

If 3layerdipstackl21ibf 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.

Is 3layerdipstackl21ibf part of a known attack campaign?

Yes — 3layerdipstackl21ibf is associated with the GHSA-m47x-cm5j-vhg2, IN-MAL-2026-018943 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find 3layerdipstackl21ibf across my projects, lockfiles, and CI pipelines?

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

Malicious package

3layerdipstackl21ibfnpm

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

Malicious code in 3layerdipstackl21ibf (npm)

MAL-2026-14810

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall 3layerdipstackl21ibf

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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

1 flagged

0.1.4

Indicators of compromise (SHA-256)

389e078a9544620ce180ef7ea567e3f498101ca0dceb77638f47b80fdf7ea524

bdc6ccc6467814c4ddf095d64904d3b0d2f475dbcd599ddcf02f43329cbdbf49

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for 3layerdipstackl21ibf (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 3layerdipstackl21ibf across your stack and pipelines.
If you installed it — respond
Remove 3layerdipstackl21ibf 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.
Did it already run?
If 3layerdipstackl21ibf 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.
How O3 protects you
O3 blocks 3layerdipstackl21ibf 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. 3layerdipstackl21ibf on npm has been identified as a malicious package (version 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m47x-cm5j-vhg2IN-MAL-2026-018943

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 3layerdipstackl21ibf-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database