Which versions of d4sp are malicious?

The following npm versions of d4sp are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate d4sp if I installed it?

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

If d4sp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is d4sp part of a known attack campaign?

Yes — d4sp is associated with the RLMA-2026-01231 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 d4sp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for d4sp (version 999.0.0).

Malicious package

d4spnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in d4sp (npm)

MAL-2026-1702

Immediate action

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

npm uninstall d4sp

What this malware does

The package d4sp was found to contain malicious code.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

db575182cd492ef27ac690b5dd0830f6e81b51f637f9cb8a13f90c44dede0b74

43442283379ac8facfef9522565bf37b744335b06deefa968f27f1ff8ed2bd8a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for d4sp (version 999.0.0).
If you installed it — respond
Remove d4sp 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 d4sp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. d4sp on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01231

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks d4sp-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