Which versions of 0xpolygonhermez are malicious?

The following npm versions of 0xpolygonhermez are flagged malicious: 6.0.0. Treat any of these as compromised.

How do I remediate 0xpolygonhermez if I installed it?

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

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

Yes — 0xpolygonhermez is associated with the RLMA-2025-02123, RLUA-2026-05951 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 0xpolygonhermez across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 0xpolygonhermez (version 6.0.0).

Malicious package

0xpolygonhermeznpm

Advisory published Apr 23, 2025Updated Sep 1, 2026

0xpolygonhermez is a confirmed malicious npm package (MAL-2025-3298) that executes malicious code on install (malicious version 6.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 0xpolygonhermez (npm)

MAL-2025-3298

Immediate action

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

npm uninstall 0xpolygonhermez

Malicious versions

1 flagged

6.0.0

Indicators of compromise (SHA-256)

dc63ff48e7bf82c9bc46f573b8a0dc598333b58ab03a6407d0aa4f6bfaaa873c

2409e2a1efc157244c12065e220f9085034bdabfe0c2d276af1afeab72c7e9b2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-02123RLUA-2026-05951

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks 0xpolygonhermez-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