Which versions of 3layerdipstackjnh4m1 are malicious?

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

How do I remediate 3layerdipstackjnh4m1 if I installed it?

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

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

Yes — 3layerdipstackjnh4m1 is associated with the GHSA-gxph-cp6j-9p53, IN-MAL-2026-018928 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 3layerdipstackjnh4m1 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 3layerdipstackjnh4m1 (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 3layerdipstackjnh4m1 across your stack and pipelines.

Malicious package

3layerdipstackjnh4m1npm

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

MAL-2026-14790

Immediate action

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

npm uninstall 3layerdipstackjnh4m1

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)

79f0d124f24c2ba2c18a57cafc75eb2209edd56308ea42f8fffdd2c94bc52a52

fbafb2120a0c1a9e305f4904a3c753b097417bf2d6ac4348ca6ff493649b0d55

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 3layerdipstackjnh4m1 (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 3layerdipstackjnh4m1 across your stack and pipelines.
If you installed it — respond
Remove 3layerdipstackjnh4m1 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 3layerdipstackjnh4m1 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 3layerdipstackjnh4m1 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. 3layerdipstackjnh4m1 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-gxph-cp6j-9p53IN-MAL-2026-018928

References

Credits

Amazon Inspector · finder

Detect & block this

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