Which versions of sf-th-requests are malicious?

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

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

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

If sf-th-requests was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is sf-th-requests part of a known attack campaign?

Yes — sf-th-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-th-requests across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sf-th-requests (2 malicious versions).

Malicious package

sf-th-requestsPyPI

Advisory published Apr 28, 2026Updated May 3, 2026

sf-th-requests is a confirmed malicious PyPI package (MAL-2026-3135) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sf-th-requests (PyPI)

MAL-2026-3135

Immediate action

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

pip uninstall sf-th-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-credentials
exfiltration-env-variables
exfiltration-cloud-tokens

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

3a4508be29963ffe0a2d8b245449cf80873bdd6037c226e94ff99d9937566c7d

f733fea099f51e19b39aca2594a21c40511e6e20af657c0f6a07339030ca0944

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for sf-th-requests (2 malicious versions).
If you installed it — respond
sf-th-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-th-requests was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sf-th-requests on PyPI has been identified as a malicious package (versions 0.1.0, 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-th-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

Explore

All malware advisories How O3 detects malware Vulnerability database