Which versions of react-adparser are malicious?

The following npm versions of react-adparser are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate react-adparser if I installed it?

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

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

Yes — react-adparser is associated with the RLMA-2025-05924, RLUA-2025-06455, RLUA-2026-01522 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 react-adparser across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-adparser (version 2.0.1).

Malicious package

react-adparsernpm

Advisory published Dec 1, 2025Updated Mar 19, 2026

react-adparser is a confirmed malicious npm package (MAL-2025-191581) that executes malicious code on install (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-adparser (npm)

MAL-2025-191581

Immediate action

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

npm uninstall react-adparser

What this malware does

The package react-adparser was found to contain malicious code.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

fd30feaaadcda73a8de726ceda65bf21cf9d642f99118d95fc740a766a833f79

dc069455c5283685b6aa5d61577633e516a1aff77cdde8844ff99bc81e2e9d94

1103c606144f791fd2418c99011dbcb6e6cf2fa10d1565edcba0dfc282fcc143

eed301ac62f5f16bace1ac0fc5ef502da8ff95838af54951e63e718d020dbc1c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05924RLUA-2025-06455RLUA-2026-01522

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks react-adparser-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