react-wp-viewernpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for react-wp-viewer (3 malicious versions).
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.
Did it already run?
If react-wp-viewer 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
Campaign
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.