Which versions of open-vp-cal are malicious?

The following PyPI versions of open-vp-cal are flagged malicious: 1.3.1. Treat any of these as compromised.

How do I remediate open-vp-cal if I installed it?

open-vp-cal 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 open-vp-cal — how do I know if it already compromised me?

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

Yes — open-vp-cal is associated with the 2026-03-open-vp-cal 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 open-vp-cal 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 open-vp-cal (version 1.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging open-vp-cal across your stack and pipelines.

Malicious package

open-vp-calPyPI

Malicious code in open-vp-cal (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2138

Immediate action

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

pip uninstall open-vp-cal

What this malware does

When executing the module, the code installs a package from a remote location. The remote package contains malicious code exfiltrating selected env variables and selected information from credential files. The code claims to be security research.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-open-vp-cal

Reasons (based on the campaign):

exfiltration-env-variables
Downloads and executes a remote malicious script.
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

1.3.1

Indicators of compromise (SHA-256)

ab8c06b5d7e9b98d62708ab7377d9e18a214e884c69b0c7217979121aed06917

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

Campaign

2026-03-open-vp-cal

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks open-vp-cal-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