Which versions of pui-diagnostics are malicious?

The following npm versions of pui-diagnostics are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate pui-diagnostics if I installed it?

Remove pui-diagnostics from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed pui-diagnostics — how do I know if it already compromised me?

If pui-diagnostics 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 pui-diagnostics part of a known attack campaign?

Yes — pui-diagnostics is associated with the GHSA-96f9-39p2-gjwm, RLMA-2026-05239, RLUA-2026-05600 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 pui-diagnostics 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 pui-diagnostics (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pui-diagnostics across your stack and pipelines.

Malicious package

pui-diagnosticsnpm

pui-diagnostics is a confirmed malicious npm package (MAL-2026-5670) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pui-diagnostics (npm)

MAL-2026-5670

Immediate action

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

npm uninstall pui-diagnostics

What this malware does

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

1 flagged

99.9.1

Indicators of compromise (SHA-256)

f05c21e14c3c230fc88a2e0513e8dcd1ba8eda06a21ee1371dd5277b4280740a

780116f7b8d93258c855180a2c7515859fa0cf634cf91f0dac2f16a81213177d

7e713dac0355b9ae36124830ae7d87f0240878f35cb920218d7c8b0074d065a2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pui-diagnostics (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pui-diagnostics across your stack and pipelines.
If you installed it — respond
Remove pui-diagnostics from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pui-diagnostics 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 pui-diagnostics 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. pui-diagnostics on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-96f9-39p2-gjwmRLMA-2026-05239RLUA-2026-05600

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks pui-diagnostics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database