pp-react-v5npm
pp-react-v5 is a confirmed malicious npm package (MAL-2026-3509) that opens a backdoor for remote access (malicious versions 10.0.0, 30.0.1, 30.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pp-react-v5 (npm)
What this malware does
pp-react-v5 is a dependency confusion package published at the inflated version 10.0.0 to win npm resolution over any internally-hosted package of the same name. The package contains only a package.json with no functional source code.
On installation the preinstall script executes a wget command that sends a GET request to http://q9ou9xtw.requestrepo.com/ with the current username (whoami), working directory (pwd), and hostname as query parameters, beaconing the victim machine's identity to the attacker-controlled endpoint.
package.json declares preinstall and postinstall hooks that execute index.js on npm install. The script collects installer host identifiers via os.hostname(), os.userInfo().username, os.homedir(), process.cwd(), dns.getServers(), and the local package.json contents, then POSTs them over HTTPS to a hardcoded interact.sh out-of-band collector subdomain at bvfmpadujgjgmbtzeibi1n3vi1psox11k.oast.fun. The package name 'pp-react-v5', the description 'Internal App bUg b0UntY gollum22 h1', and the inflated 30.0.1 version are consistent with a dependency-confusion probe targeting an internal package name. Installing this package results in unauthenticated disclosure of installer identity, environment, and repository metadata to an attacker-controlled collector.
The OpenSSF Package Analysis project identified 'pp-react-v5' @ 10.0.0 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
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 pp-react-v5 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pp-react-v5 across your stack and pipelines.
If you installed it — respond
pp-react-v5 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 pp-react-v5 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 pp-react-v5 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
- OpenSSF: Package Analysis · finder
- SafeDep · finder
Detect & block this
O3 blocks pp-react-v5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.