Which versions of pvd3 are malicious?

The following npm versions of pvd3 are flagged malicious: 99.9.0, 99.9.9. Treat any of these as compromised.

How do I remediate pvd3 if I installed it?

Remove pvd3 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 pvd3 — how do I know if it already compromised me?

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

Yes — pvd3 is associated with the GHSA-4m95-g5w6-4x4w, RLMA-2026-05241, RLUA-2026-05601 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 pvd3 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 pvd3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pvd3 across your stack and pipelines.

Malicious package

pvd3npm

pvd3 is a confirmed malicious npm package (MAL-2026-6669) that executes malicious code on install (malicious versions 99.9.0, 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pvd3 (npm)

MAL-2026-6669

Immediate action

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

npm uninstall pvd3

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

2 flagged

99.9.099.9.9

Indicators of compromise (SHA-256)

0c992d4bd87c36aa389d168c263ca0b89c04b425b0483217ae1098a0c2f3ee10

da6eb38543c306cc9b19aef58205c5b3741f3d5fa4e9c4d88efc1b3fe6df1dea

216adcbfc9d7399b8fbb779d3f8ac6ab27dd8126839b33cb7b9ef1ab05f77b35

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 pvd3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pvd3 across your stack and pipelines.
If you installed it — respond
Remove pvd3 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 pvd3 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 pvd3 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. pvd3 on npm has been identified as a malicious package (versions 99.9.0, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4m95-g5w6-4x4wRLMA-2026-05241RLUA-2026-05601

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks pvd3-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