Which versions of pp-react-ui5 are malicious?

The following npm versions of pp-react-ui5 are flagged malicious: 21.0.0, 28.0.0. Treat any of these as compromised.

How do I remediate pp-react-ui5 if I installed it?

pp-react-ui5 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.

I already installed pp-react-ui5 — how do I know if it already compromised me?

If pp-react-ui5 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.

Is pp-react-ui5 part of a known attack campaign?

Yes — pp-react-ui5 is associated with the GHSA-6h4j-g3j5-97rc, IN-MAL-2026-011132, IN-MAL-2026-013199 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find pp-react-ui5 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pp-react-ui5 (2 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-ui5 across your stack and pipelines.

Malicious package

pp-react-ui5npm

pp-react-ui5 is a confirmed malicious npm package (MAL-2026-11059) that steals credentials and exfiltrates sensitive data (malicious versions 21.0.0, 28.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pp-react-ui5 (npm)

MAL-2026-11059

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall pp-react-ui5

What this malware does

Analysis of [email protected] (4 files) surfaced no behaviors matching supply-chain attack classes: no lifecycle scripts fetching or executing remote content, no reads of installer credential paths (~/.npmrc, ~/.aws, ~/.ssh, browser profiles), no environment-variable scraping, no hardcoded exfiltration endpoints, no obfuscated payloads, and no backdoor or silent-relay mechanisms observed. The package appears benign under the criteria evaluated here.

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.

The OpenSSF Package Analysis project identified 'pp-react-ui5' @ 28.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

21.0.028.0.0

Indicators of compromise (SHA-256)

8814d99d507641e7c51946441bfb107e3ec32887792bb9a3ace1d638e688c8f8

6f33e8ad4e8e4d1037b0532607e4ddc2a7b9738ce59388d7258dbcc285ac900d

99877752005feb09afa72d4502ff83082df6774eb3f86b7fba2122e6f38b4a7c

fee26042aed9ed8c50ffaa9b8fd40df265099c14441c38542bbfce3c529ceef3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pp-react-ui5 (2 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-ui5 across your stack and pipelines.
If you installed it — respond
pp-react-ui5 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 pp-react-ui5 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-ui5 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. pp-react-ui5 on npm has been identified as a malicious package (versions 21.0.0, 28.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6h4j-g3j5-97rcIN-MAL-2026-011132IN-MAL-2026-013199

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database