Which versions of 3layerdipstackr7ib9k are malicious?

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

How do I remediate 3layerdipstackr7ib9k if I installed it?

Remove 3layerdipstackr7ib9k 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 3layerdipstackr7ib9k — how do I know if it already compromised me?

If 3layerdipstackr7ib9k 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 3layerdipstackr7ib9k part of a known attack campaign?

Yes — 3layerdipstackr7ib9k is associated with the GHSA-mr3w-g49x-qcm3, IN-MAL-2026-018991 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 3layerdipstackr7ib9k 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 3layerdipstackr7ib9k (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 3layerdipstackr7ib9k across your stack and pipelines.

Malicious package

3layerdipstackr7ib9knpm

3layerdipstackr7ib9k is a confirmed malicious npm package (MAL-2026-14899) 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 3layerdipstackr7ib9k (npm)

MAL-2026-14899

Immediate action

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

npm uninstall 3layerdipstackr7ib9k

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)

cafcdd6bc69ca87bef7a5d388003d5874d2d4eb6c7ea58e62a0ef50afa0206fe

4e700d8fdf8a230a433bbf1fc3084c4a823335f7fbf4b2bca2ab54595564deed

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 3layerdipstackr7ib9k (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 3layerdipstackr7ib9k across your stack and pipelines.
If you installed it — respond
Remove 3layerdipstackr7ib9k 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 3layerdipstackr7ib9k 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 3layerdipstackr7ib9k 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. 3layerdipstackr7ib9k 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-mr3w-g49x-qcm3IN-MAL-2026-018991

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 3layerdipstackr7ib9k-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