Which versions of react-puller are malicious?

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

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

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

If react-puller was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is react-puller part of a known attack campaign?

Yes — react-puller is associated with the IN-MAL-2026-010939 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-puller across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-puller (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-puller across your stack and pipelines.

Malicious package

react-pullernpm

react-puller is a confirmed malicious npm package (MAL-2026-11144) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-puller (npm)

MAL-2026-11144

Immediate action

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

npm uninstall react-puller

What this malware does

The package's postinstall hook runs node index.js, which spawns a detached worker that downloads two Windows executables (CDPUserPlatform.exe and DOContentCacheMgr.exe) from a hardcoded bare-IP endpoint at http://64.49.11.161:8000 over plain HTTP, writes them into ~/.react-pul, and launches them via cmd /c start. The addToStartup routine then writes an HKCU\Software\Microsoft\Windows\CurrentVersion\Run entry pointing at ~/.react-pul/DOContentCacheMgr.exe, autostarting the dropped binary on every user login. The package name and description present it as a generic React utility, unrelated to the shipped behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a3ac07c0f6c79714a7b1f6bfd1272f9f7942cf0473875ca5276a1034c084f06d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-puller (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-puller across your stack and pipelines.
If you installed it — respond
Remove react-puller 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-puller was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks react-puller before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. react-puller on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010939

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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