Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

react-wp-viewernpm

react-wp-viewer is a confirmed malicious npm package (MAL-2026-6571) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.4, 0.2.15, 0.2.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-wp-viewer (npm)

MAL-2026-6571
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-wp-viewer

What this malware does

react-wp-viewer 0.2.4 is a dependency-confusion package. Its postinstall hook performs an HTTP GET to a hardcoded bare-IP endpoint at http://130.49.177.51:18080/p/dc-20260627-yandex-geobase carrying the package name, version, and a fixed nonce. The package self-identifies as a dependency-confusion proof-of-concept (__dependency_confusion_poc__: true) and the URL path encodes a campaign identifier referencing an internal package namespace, indicating the public name is being squatted to win resolution against an identically-named private/internal package. Any build that resolves react-wp-viewer from the public registry will silently execute the postinstall beacon, disclosing the installer's source IP, hostname-derived network position, and the fact that this internal name resolves within their environment, to an attacker-controlled host over plain HTTP. No installer credentials are read in the traced code, but the install-time callout to an attacker-controlled IP is the dependency-confusion attack pattern and provides material reconnaissance value to the operator.

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.

Malicious versions

3 flagged
0.2.40.2.150.2.99

Indicators of compromise (SHA-256)

08fd73c12a730e8dfbaa5bf21aa086a0a3de88241fbd6d880a20805838929572
443f37b7957fe3f1d4dd836b3a0e6eeddb513e334700e0c0a4616570071c13d8
5b9202fdee16d26d0f7484f7f9a0d2d264b38ad3200b396ef483cc2439225360
dae245d908c5e9ae1001f2590c5d362fa1f21e148cdf565487424fabdad44700

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-wp-viewer (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-wp-viewer across your stack and pipelines.

  2. If you installed it — respond

    react-wp-viewer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If react-wp-viewer 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.

  4. How O3 protects you

    O3 blocks react-wp-viewer 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

No. react-wp-viewer on npm has been identified as a malicious package (versions 0.2.4, 0.2.15, 0.2.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007713IN-MAL-2026-007715IN-MAL-2026-007714GHSA-566x-g457-qg8g

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks react-wp-viewer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

react-wp-viewer (npm) malicious package — MAL-2026-6571 | O3 Security