Which versions of picnic-decoder-generator are malicious?

The following npm versions of picnic-decoder-generator are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate picnic-decoder-generator if I installed it?

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

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

Yes — picnic-decoder-generator is associated with the RLMA-2026-05211, RLUA-2026-06371 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 picnic-decoder-generator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for picnic-decoder-generator (version 9999.0.0).

Malicious package

picnic-decoder-generatornpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

picnic-decoder-generator is a confirmed malicious npm package (MAL-2026-7340) that executes malicious code on install (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in picnic-decoder-generator (npm)

MAL-2026-7340

Immediate action

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

npm uninstall picnic-decoder-generator

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

e7d462a15f19ae9e9d99ddbafdd17585f5b72063bfdd9a8d93766531859ecf56

4fc66f4e570467caf20c0cd44e261050944f5ba079a0fcd7441c61c0717be8f8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for picnic-decoder-generator (version 9999.0.0).
If you installed it — respond
Remove picnic-decoder-generator 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 picnic-decoder-generator 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. picnic-decoder-generator on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05211RLUA-2026-06371

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks picnic-decoder-generator-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