NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

pp-react-v5npm

Advisory published Updated

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)

MAL-2026-3509
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pp-react-v5

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

3 flagged
10.0.030.0.130.0.2

Indicators of compromise (SHA-256)

b2291adfbdded958f2fa2a51aa5e582d8ec4bad5bb1c5c9b614bd496732c3578
667950ffe2ed24a98495c0d8d6c3430e3538523c5811caf9fbda829b0773163f
7b6506f382410337abd6bc9f24c3108c52ce25f6b359537fda9e9dabb9e077f3
f2ada661adc926404648a9955aaad5c4faefaf24937ec8a75df2deaf0f09716c
4f6647a874d9c2f5e2a9fe92465f1f690563ebd589dd4e5334a24db89e164972

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for pp-react-v5 (3 malicious versions).

  2. 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.

  3. Did it already run?

    If pp-react-v5 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. pp-react-v5 on npm has been identified as a malicious package (versions 10.0.0, 30.0.1, 30.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009263IN-MAL-2026-009348

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.

Explore

pp-react-v5 (npm) malicious package — MAL-2026-3509 | O3 Security