Which versions of penny-core are malicious?

The following npm versions of penny-core are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate penny-core if I installed it?

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

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

Yes — penny-core is associated with the RLMA-2026-05210, RLUA-2026-06370 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 penny-core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for penny-core (version 99.0.1).

Malicious package

penny-corenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in penny-core (npm)

MAL-2026-7339

Immediate action

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

npm uninstall penny-core

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

84022e2b7470958530d0c5148c02e9fd7811f77f4ff57923beb155e8d383f237

ef6fac87c839c31657385e08f03488ad7b40983c3c17661e45069a8006228477

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05210RLUA-2026-06370

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks penny-core-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