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

flask-auth-systemPyPI

Malicious code in flask-auth-system (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191731
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall flask-auth-system

What this malware does

On importing the module, the code attempts to span a reverse shell. In the current version, the remote domain does not exist

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

Campaign: 2025-04-flask-auth-sys

Reasons (based on the campaign):

  • dependency-confusion

  • The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

  • obfuscation

Malicious versions

2 flagged
0.0.10.0.2

Indicators of compromise (SHA-256)

c934eee6779ff735799b39b4a5355c0931e30914a49500afd183f066ec4af683
debc87eb7af33e5146831c7e1b8ff69ccdebe2c9bbf353216c719b10ebe8431c
83c824d3eff87fd20e3730c2d2b3cc52987ba4fb1e667448e35b453679c5bbd6

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 flask-auth-system (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flask-auth-system across your stack and pipelines.

  2. If you installed it — respond

    flask-auth-system 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 flask-auth-system 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 flask-auth-system 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. flask-auth-system on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-04-flask-auth-sys

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

O3 blocks flask-auth-system-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

flask-auth-system (PyPI) malicious package — MAL-2025-191731 | O3 Security