Which versions of react-campaign-optimizer are malicious?

The following npm versions of react-campaign-optimizer are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate react-campaign-optimizer if I installed it?

react-campaign-optimizer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed react-campaign-optimizer — how do I know if it already compromised me?

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

Yes — react-campaign-optimizer is associated with the IN-MAL-2026-007437, IN-MAL-2026-007436, GHSA-m55j-v4cf-p5w5 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-campaign-optimizer 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-campaign-optimizer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-campaign-optimizer across your stack and pipelines.

Malicious package

react-campaign-optimizernpm

Malicious code in react-campaign-optimizer (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6395

Immediate action

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

npm uninstall react-campaign-optimizer

What this malware does

On npm install, the package runs node postinstall.js (declared in package.json scripts.postinstall) which performs unauthenticated, unconsented exfiltration to the hardcoded attacker endpoint https://2e3bkumw.requestrepo.com. The script collects and POSTs: full process.env (line 60), hostname and host metadata (os.hostname(), network interfaces, routes, ARP, DNS config, /etc/hosts, ps/netstat/lsof output), and the contents of canonical credential files including /root/.ssh/id_rsa, ~/.ssh/authorized_keys, /etc/shadow, /root/.kube/config, /root/.docker/config.json, /root/.npmrc, /root/.gitconfig, /root/.bash_history, and the in-pod Kubernetes ServiceAccount token at /var/run/secrets/kubernetes.io/serviceaccount/token. It additionally probes cloud-metadata IPs (169.254.169.254, 100.100.100.200, 169.254.0.23) for IAM credentials and TCP-scans local /24 ranges for service ports (SSH, MySQL, Redis, Docker API 2375, etcd 2379, K8s API, Prometheus, Grafana), shipping results to the same callback. The package presents itself as a React ad-campaign optimization utility (description, keywords baidu/sem/ppc) but ships no React or ad-tech code — index.js is unrelated and the postinstall payload is a Baidu-infrastructure-targeted recon/credential-theft script (header comment: 百度基础设施 SSRF 探测). The 'authorized security testing' self-label is not consent: the package is published publicly on npm and fires for any installer. Any CI runner, developer machine, or container that installs this package leaks SSH private keys, kube credentials, npm publish tokens, K8s ServiceAccount tokens, and cloud IAM metadata to the attacker.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

68f544f6c96c586e8d0659312bd645e449760e89006aca3fa47bd49161c5e6e2

a040ca9a32fe68e08906bdc58b7ae907b8f8092acd9764266de15004b3922e9f

026137182a42d12b815aad9476d92769953101cb32a88c4a5329ca9318a6bb35

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-campaign-optimizer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-campaign-optimizer across your stack and pipelines.
If you installed it — respond
react-campaign-optimizer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If react-campaign-optimizer 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-campaign-optimizer 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-campaign-optimizer on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007437IN-MAL-2026-007436GHSA-m55j-v4cf-p5w5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-campaign-optimizer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring