Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

sf-silly-goose-requestsPyPI

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

MAL-2026-5184
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall sf-silly-goose-requests

What this malware does

Package uses trufflehog to detect secrets and exfiltrates them to a hardcoded location

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

Campaign: 2026-06-sf-silly-goose-requests

Reasons (based on the campaign):

  • exfiltration-credentials

  • exfiltration-env-variables

Malicious versions

2 flagged
0.1.00.2.0

Indicators of compromise (SHA-256)

d1b2d16ce881d1e9b356ed424f8144ce9324d09010efa8761ad13ac8a46e7b60
a408d377936e3acbf92e1aa97b7ae20de4af6f07bbd02f1e2bb24300be4e12c0

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sf-silly-goose-requests (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sf-silly-goose-requests across your stack and pipelines.

  2. If you installed it — respond

    sf-silly-goose-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.

  3. Did it already run?

    If sf-silly-goose-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.

  4. How O3 protects you

    O3 blocks sf-silly-goose-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-silly-goose-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-06-sf-silly-goose-requests

References

Credits

  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks sf-silly-goose-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.

sf-silly-goose-requests (PyPI) malicious package — MAL-2026-5184 | O3 Security