Which versions of dist-decoder are malicious?

The following npm versions of dist-decoder are flagged malicious: 2.0.3, 2.0.4. Treat any of these as compromised.

How do I remediate dist-decoder if I installed it?

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

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

Yes — dist-decoder is associated with the GHSA-458p-6fw4-4v56, RLMA-2025-05768, RLUA-2025-06113 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 dist-decoder 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 dist-decoder (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dist-decoder across your stack and pipelines.

Malicious package

dist-decodernpm

dist-decoder is a confirmed malicious npm package (MAL-2025-48518) that executes malicious code on install (malicious versions 2.0.3, 2.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dist-decoder (npm)

MAL-2025-48518

Immediate action

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

npm uninstall dist-decoder

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

2 flagged

2.0.32.0.4

Indicators of compromise (SHA-256)

9d6276f9115715018347a416b17686c81064ab130b386dacfdbe52f80bf1a2d4

9ec354cbb01d7815f8a937685c895e973ed35d7ea408e35fb2de1d8b2c4c2b88

d2e924557725b13c4a217073a1540811bcc39b188252306aef2a53c47d730f61

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 dist-decoder (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dist-decoder across your stack and pipelines.
If you installed it — respond
Remove dist-decoder 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 dist-decoder 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 dist-decoder 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. dist-decoder on npm has been identified as a malicious package (versions 2.0.3, 2.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-458p-6fw4-4v56RLMA-2025-05768RLUA-2025-06113

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dist-decoder-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