Which versions of astronomios are malicious?

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

How do I remediate astronomios if I installed it?

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

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

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

Malicious package

astronomiosPyPI

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

MAL-2025-1964

Immediate action

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

pip uninstall astronomios

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)

fc415dfc4274d891bab6cab0c52a6d50f6ed85c4a5a15cc4a7eccaf1147204e1

6edfbcc895cbfd69fb42f2be18d76f510f3770a01f896d9eb2213701d565ad66

44bb8480782438fda3365b0ffcc74a04ae68477448d543ae51c1744b0cdb4a77

981890ec9e60b6d34f7844c7a9a2e07dab6ccd928616537bac2b50bc56d01c96

fc58d82dbbceb4abf143cd17fa209117f967088309c0bf9f6c5f068602a18d13

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 astronomios (version 0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging astronomios across your stack and pipelines.
If you installed it — respond
astronomios 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 astronomios 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 astronomios 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. astronomios 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-011992025-02-astronomioRLUA-2026-00085

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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