Which versions of astronomio are malicious?

The following PyPI versions of astronomio are flagged malicious: 0.5. Treat any of these as compromised.

How do I remediate astronomio if I installed it?

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

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

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

Malicious package

astronomioPyPI

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

MAL-2025-1963

Immediate action

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

pip uninstall astronomio

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.5

Indicators of compromise (SHA-256)

2554b538538908997b6615b6c25c5662287f2f4198397eed2ef00fda6e7447d6

b04331799550bdca854125230023e2e7d0ecef25d61741aa629a69ed3a508d98

083fa61d5e589b627ba6c1d6db2db22ef6df9cd06e6df5bda08120e2c65bb20d

7551be6c6385de139128aba09bb9b2f0fa985881201f999afac66af384c2195b

414b6baaf81da821721002c4e9c3a0742fda87ea21160d8eabecea9363db4efc

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

Campaign

RLMA-2025-011982025-02-astronomioRLUA-2026-00084

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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