ultimate-ai-powerPyPI
Malicious code in ultimate-ai-power (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
On import ultimate_ai_power, the package's top-level init.py collects the local username (getpass.getuser) and resolved host IP (socket.gethostbyname) and POSTs them to a hardcoded Telegram Bot API endpoint (bot token 8844473290:AAGY..., chat_id 7095972030); a second beacon is sent via an atexit handler. The advertised AI functions (ai_power_boost, neural_enhance, quantum_compute) are placeholders that return constant strings — the package has no real functionality beyond the exfiltration beacon. Metadata uses a placeholder author 'AI Innovation Labs' with a non-existent GitHub org. Cover-story messages in the beacon payload are written in Russian. Any installer who imports the package leaks identifying host/user information to the attacker.
Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.
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: GENERIC-standard-pypi-install-pentest
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.
-
The package overrides the install command in setup.py to execute malicious code during installation.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ultimate-ai-power (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ultimate-ai-power across your stack and pipelines.
If you installed it — respond
ultimate-ai-power 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 ultimate-ai-power 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 ultimate-ai-power 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · analyst
Detect & block this
O3 blocks ultimate-ai-power-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.