Which versions of automsg are malicious?

The following PyPI versions of automsg are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate automsg if I installed it?

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

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

Yes — automsg is associated with the RLMA-2024-07845, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00125 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 automsg 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 automsg (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging automsg across your stack and pipelines.

Malicious package

automsgPyPI

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

MAL-2024-9948

Immediate action

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

pip uninstall automsg

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4a7c87cde06fbc0379e2d1f1020cc533e06c3dd3556aa51195c46920364f6911

b9e29abb753566c2df63534c5ad9073a0ca4ffd10400ec0a435d9df292c77007

a96ae8403b713d8dbe1fbb5e8a17e2e06d08740e459e90b03769d5dfc7da33d9

8d472404799b7ad5d5e3da92fc788dc026e33213a7037efce6f67065b4f4f1dd

e6cff992609b9c5cf8cff19f7210a40c306b7ffe67b818dfd05cbaee87194433

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

Campaign

RLMA-2024-078452024-08-embeds-RealtekHDAudioManagerRLUA-2026-00125

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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