Which versions of 3layerdipstackkl17i are malicious?

Every published version of 3layerdipstackkl17i on npm is considered malicious. Remove the package entirely.

How do I remediate 3layerdipstackkl17i if I installed it?

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

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

Yes — 3layerdipstackkl17i is associated with the GHSA-65h5-ffqr-4rwv 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 3layerdipstackkl17i 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 3layerdipstackkl17i (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 3layerdipstackkl17i across your stack and pipelines.

Malicious package

3layerdipstackkl17inpm

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

Malicious code in 3layerdipstackkl17i (npm)

MAL-2026-14802

Immediate action

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

npm uninstall 3layerdipstackkl17i

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)

b0eebc3695528bc0f65578c14bbc130de49dff7dc0cef6a6faa1eedac884e9fe

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 3layerdipstackkl17i (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 3layerdipstackkl17i across your stack and pipelines.
If you installed it — respond
Remove 3layerdipstackkl17i 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 3layerdipstackkl17i 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 3layerdipstackkl17i 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. 3layerdipstackkl17i 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-65h5-ffqr-4rwv

References

github.com

Detect & block this

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