Which versions of astrono2mio are malicious?

The following PyPI versions of astrono2mio are flagged malicious: 0.6. Treat any of these as compromised.

How do I remediate astrono2mio if I installed it?

astrono2mio 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 astrono2mio — how do I know if it already compromised me?

If astrono2mio 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 astrono2mio part of a known attack campaign?

Yes — astrono2mio is associated with the RLMA-2025-01197, 2025-02-astronomio, RLUA-2026-00083 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 astrono2mio 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 astrono2mio (version 0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging astrono2mio across your stack and pipelines.

Malicious package

astrono2mioPyPI

Malicious code in astrono2mio (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-1962

Immediate action

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

pip uninstall astrono2mio

What this malware does

setup.py contains highly obfuscated infostealer

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

Campaign: 2025-02-astronomio

Reasons (based on the campaign):

infostealer
dependency-confusion
obfuscation
exfiltration-browser-data
exfiltration-crypto

Malicious versions

1 flagged

0.6

Indicators of compromise (SHA-256)

1112e79b4907928f3f24161bf74faab51942ee30d6a59d8a7a491d30719e26c3

d88ee9c1f73faaf46a1674cfc815eb2288282d0ffcb39506bbc74ae966cf47a6

5afe73e89e82bc8240384de865b69392288e63d7612b403c8ce3a6c6f42273cb

d0ba3d5f73ed5ee02c92e6bda2d9913445fbaad16d102a75ae9f31df7e547f96

187d71f740cf34f524ac7fb3a04de71869bac7bef4ce3717d27e946bc17a4226

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 astrono2mio (version 0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging astrono2mio across your stack and pipelines.
If you installed it — respond
astrono2mio 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 astrono2mio 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 astrono2mio 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. astrono2mio on PyPI has been identified as a malicious package (version 0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-011972025-02-astronomioRLUA-2026-00083

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks astrono2mio-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