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

aws-consoler2PyPI

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

MAL-2023-8358
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall aws-consoler2

What this malware does

Malicious Typosquatting packages campaign targeting developers, steals cloud service credentials

Attack targeted at users of Alibaba, AWS and Telegram via malicious packages published to PyPI.

The malicious code was hidden in strategicly chosen functions and would only trigger when these functions were called. The malicious code does not automatically run on install or import, helping the packages evade detection.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

24f9ca302dd0a2aabb28a665dbf8cdd392abc96f92dda8f8b994bf46836621cc
b37bd86b6f9bda9d03029c9d2fa09561b2b43cda7c3fddda1389c8e193c4a938

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

  2. If you installed it — respond

    aws-consoler2 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 aws-consoler2 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 aws-consoler2 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. aws-consoler2 on PyPI has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Checkmarx · finder

Detect & block this

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

aws-consoler2 (PyPI) malicious package — MAL-2023-8358 | O3 Security