# MAL-2026-5458: Malicious code in ultimate-ai-power (PyPI)


- **Type:** Malicious package
- **Package:** `ultimate-ai-power` (PyPI)
- **Published:** 9 Jun 2026

## What is MAL-2026-5458?

MAL-2026-5458 is a malicious package in ultimate-ai-power, published on 9 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-5458?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5458 is a malicious package: ultimate-ai-power (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5458/ (Markdown: https://insights.sbomify.com/MAL-2026-5458/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5458

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5458/
Summaries are generated and may contain mistakes; the official description above is the record.