Which versions of 3layerdipstack4ilqnj are malicious?

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

How do I remediate 3layerdipstack4ilqnj if I installed it?

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

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

Yes — 3layerdipstack4ilqnj is associated with the GHSA-5x58-fpvh-r4q4, IN-MAL-2026-018833 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 3layerdipstack4ilqnj 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 3layerdipstack4ilqnj (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 3layerdipstack4ilqnj across your stack and pipelines.

Malicious package

3layerdipstack4ilqnjnpm

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

MAL-2026-14625

Immediate action

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

npm uninstall 3layerdipstack4ilqnj

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)

d397e887972e675f732dfe7744d07134283e57d8a29af6a333c74e095fb65ff6

928bde04253d6eb906a30623cb658894bab1a8415aa829674556a74a1a067475

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 3layerdipstack4ilqnj (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 3layerdipstack4ilqnj across your stack and pipelines.
If you installed it — respond
Remove 3layerdipstack4ilqnj 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 3layerdipstack4ilqnj 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 3layerdipstack4ilqnj 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. 3layerdipstack4ilqnj 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-5x58-fpvh-r4q4IN-MAL-2026-018833

References

Credits

Amazon Inspector · finder

Detect & block this

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