Which versions of sf-vmeval-requests are malicious?

The following PyPI versions of sf-vmeval-requests are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate sf-vmeval-requests if I installed it?

sf-vmeval-requests 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 sf-vmeval-requests — how do I know if it already compromised me?

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

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

Malicious package

sf-vmeval-requestsPyPI

Malicious code in sf-vmeval-requests (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3242

Immediate action

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

pip uninstall sf-vmeval-requests

What this malware does

During import package exfiltrates the environment variables and cloud credentials/tokens to a hardcoded location.

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

Campaign: 2026-04-sf-th-requests

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

a8fa27c8dc6bf13a4f5d92f14414a4f5efc08c1df7f33591a010b4f824e84bc1

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

Campaign

2026-04-sf-th-requests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks sf-vmeval-requests-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