Which versions of evil-helper-pkg are malicious?

The following npm versions of evil-helper-pkg are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate evil-helper-pkg if I installed it?

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

If evil-helper-pkg 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 evil-helper-pkg part of a known attack campaign?

Yes — evil-helper-pkg is associated with the RLMA-2026-05078, RLUA-2026-06226 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 evil-helper-pkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for evil-helper-pkg (version 1.0.2).

Malicious package

evil-helper-pkgnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

evil-helper-pkg is a confirmed malicious npm package (MAL-2026-7282) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in evil-helper-pkg (npm)

MAL-2026-7282

Immediate action

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

npm uninstall evil-helper-pkg

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

aef4a843c3ff9a943f16e724d39605eb7dc17c95da631e55d8626ae62e1f2ac7

691a47357a4686068646536ba9ea606e9b5d7296c0315f5bcba9bac1bc8b589a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05078RLUA-2026-06226

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks evil-helper-pkg-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