What does the aiogram-3 malware do?

During installation or importing the module, the package starts a reverse shell to hardcoded locatiom Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-12-aiogram-sever-patch Reasons (based on the campaign): - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - The package overrides the install command in setup.py to execute malicious code during installation. - dependency-confusion

Which versions of aiogram-3 are malicious?

The following PyPI versions of aiogram-3 are flagged malicious: 1.0.0, 10.0.0. Treat any of these as compromised.

How do I remediate aiogram-3 if I installed it?

aiogram-3 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.

I already installed aiogram-3 — how do I know if it already compromised me?

If aiogram-3 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.

Is aiogram-3 part of a known attack campaign?

Yes — aiogram-3 is associated with the 2025-12-aiogram-sever-patch campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find aiogram-3 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aiogram-3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiogram-3 across your stack and pipelines.

Malicious package

aiogram-3PyPI

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

MAL-2025-192940

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall aiogram-3

What this malware does

During installation or importing the module, the package starts a reverse shell to hardcoded locatiom

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

Campaign: 2025-12-aiogram-sever-patch

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
The package overrides the install command in setup.py to execute malicious code during installation.
dependency-confusion

Malicious versions

2 flagged

1.0.010.0.0

Indicators of compromise (SHA-256)

3d8dac0d1eb98dbfc0fe46cabeadb550699f5e41b5d033ded073f7572f450bf7

6b5a631fb392aa1f6da062744c3e022197ccd3fa71cd3480d9dc401ba4ff8d3c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aiogram-3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiogram-3 across your stack and pipelines.
If you installed it — respond
aiogram-3 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 aiogram-3 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 aiogram-3 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. aiogram-3 on PyPI has been identified as a malicious package (versions 1.0.0, 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-aiogram-sever-patch

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks aiogram-3-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