Which versions of sorex are malicious?

The following PyPI versions of sorex are flagged malicious: 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 1.0.0, 1.1.0, 1.1.9. Treat any of these as compromised.

How do I remediate sorex if I installed it?

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

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

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

Malicious package

sorexPyPI

Malicious code in sorex (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191873

Immediate action

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

pip uninstall sorex

What this malware does

Clones of libraries to access Aminoapps (e.g. legitimate package amino.fix) with added exfiltration of the given credentials

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

Campaign: 2025-06-sorex

Reasons (based on the campaign):

exfiltration-credentials
action-hidden-in-lib-usage
clones-real-package

Malicious versions

9 flagged

0.3.00.4.00.5.00.6.00.7.00.8.01.0.01.1.01.1.9

Indicators of compromise (SHA-256)

b3e73ea60d5e899bb3417b2445c911da59d926ed609dfbb0fc63d80dfdef8c7e

9fc62b886698742e247a58de03e45e48cc06149abb4e65e77df10984818ed4f1

1ac5744723cdd90a82bfd41348056dd50d1e1da4ed69d3114a8994998a8733fd

4eed29287bd3b107adf7025593709ca8943dec04c32915773804734b0ad9d987

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 sorex (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sorex across your stack and pipelines.
If you installed it — respond
sorex 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 sorex 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 sorex 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. sorex on PyPI has been identified as a malicious package (versions 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 1.0.0, 1.1.0, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-06-sorex

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks sorex-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