MAL-2026-6395 Malicious code in react-campaign-optimizer (npm)
- Package
- react-campaign-optimizer
- Registry
- npm
What is MAL-2026-6395?
MAL-2026-6395 is a malicious package in react-campaign-optimizer, published on 24 Jun 2026.
Official description
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.
What should I do about MAL-2026-6395?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-m55j-v4cf-p5w5.