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

ic-flows-platformPyPI

Malicious code in ic-flows-platform (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10582
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall ic-flows-platform

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

  • The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

  • typosquatting

  • dependency-confusion

The OpenSSF Package Analysis project identified 'ic-flows-platform' @ 91.6 (pypi) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
91.6

Indicators of compromise (SHA-256)

dc05fb08e4b8eb3adc20c8ac44ecf4800fa3f3e8bc0ac2f19f397485bc91b79c
80910a323701fed00b66593dd2e53055be6fac386390d8bb56be697dd3a73abc
7ddd18ddba219f2d0fe4c9bceab7e456d97d23dd4ba95b9cecd06bffecef2bef
18f4e99259005ef2058bb3c68bb9a59e13c7411997246f9e1a3dd657690acf65

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 ic-flows-platform (version 91.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ic-flows-platform across your stack and pipelines.

  2. If you installed it — respond

    ic-flows-platform 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 ic-flows-platform 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 ic-flows-platform 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. ic-flows-platform on PyPI has been identified as a malicious package (version 91.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

Credits

  • Kamil Mańkowski (kam193)
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ic-flows-platform-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