Which versions of vpi-guides are malicious?

Every published version of vpi-guides on npm is considered malicious. Remove the package entirely.

How do I remediate vpi-guides if I installed it?

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

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

Yes — vpi-guides is associated with the GHSA-wx4g-457v-96wq 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 vpi-guides 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 vpi-guides (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vpi-guides across your stack and pipelines.

Malicious package

vpi-guidesnpm

Malicious code in vpi-guides (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3285

Immediate action

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

npm uninstall vpi-guides

What this malware does

The package vpi-guides was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

28248d8cb6eca76057853d4e6ed366107e13c7dce9b6f02d9afd82475152a369

0746aaba735c5411a6b2e62e27b52b39aace59ceebe307f3cd192fbf052b387a

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

Campaign

GHSA-wx4g-457v-96wq

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vpi-guides-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