Which versions of pyregions-snowflake are malicious?

The following PyPI versions of pyregions-snowflake are flagged malicious: 3.9.1, 3.9.2, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.8, 3.9.9, 3.9.10. Treat any of these as compromised.

How do I remediate pyregions-snowflake if I installed it?

pyregions-snowflake 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 pyregions-snowflake — how do I know if it already compromised me?

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

Yes — pyregions-snowflake is associated with the 2026-02-urllib-slim 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 pyregions-snowflake 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 pyregions-snowflake (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyregions-snowflake across your stack and pipelines.

Malicious package

pyregions-snowflakePyPI

Malicious code in pyregions-snowflake (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2109

Immediate action

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

pip uninstall pyregions-snowflake

What this malware does

During installation, the package starts obfuscated code that downloads and runs remote executables in specific environments - in older packages - attempts to exfiltrate some basic information using DNS requests and then likely cover tracks by installing a similarly named package from private repository

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

Campaign: 2026-02-urllib-slim

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
obfuscation
dependency-confusion

Malicious versions

9 flagged

3.9.13.9.23.9.43.9.53.9.63.9.73.9.83.9.93.9.10

Indicators of compromise (SHA-256)

4c3a6759d779c0fe3ffac5559aa5f8915f72cab6bce545e1fe261f3caab47a65

4587ab1d4e7fe2fd218e9415bcb5bae29525c377f49991357e58fd8015adb991

d9847b502b8e8d469c80dd55d45273c9ab932eb73f879c6486af87f071490f80

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 pyregions-snowflake (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyregions-snowflake across your stack and pipelines.
If you installed it — respond
pyregions-snowflake 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 pyregions-snowflake 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 pyregions-snowflake 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. pyregions-snowflake on PyPI has been identified as a malicious package (versions 3.9.1, 3.9.2, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.8, 3.9.9, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-urllib-slim

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pyregions-snowflake-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