@espn-ping/react-dmed-oauthnpm
Malicious code in @espn-ping/react-dmed-oauth (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
@espn-ping/[email protected] declares a preinstall lifecycle script (node index.js > /dev/null 2>&1) that automatically executes on npm install. index.js shells out via child_process.exec to collect the installer's hostname, current working directory, username, and public IP (via curl https://ifconfig.me), then transmits the encoded data via curl -k GET to https://r.dontvisitmy.website/sendreq.php?newdata=.... Output is suppressed to hide the beacon from the installer's console. The scope @espn-ping and version 666.0.0 are consistent with a dependency-confusion beacon targeting an internal ESPN/Disney namespace.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @espn-ping/react-dmed-oauth (version 666.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @espn-ping/react-dmed-oauth across your stack and pipelines.
If you installed it — respond
@espn-ping/react-dmed-oauth establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @espn-ping/react-dmed-oauth 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 @espn-ping/react-dmed-oauth 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @espn-ping/react-dmed-oauth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.