react-campaign-optimizer @1.0.1

Summary

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.

Source: amazon-inspector (a040ca9a32fe68e08906bdc58b7ae907b8f8092acd9764266de15004b3922e9f)