Which versions of pyadd are malicious?

The following PyPI versions of pyadd are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate pyadd if I installed it?

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

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

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

Malicious package

pyaddPyPI

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

MAL-2024-10111

Immediate action

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

pip uninstall pyadd

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

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

9cb98ba09efcb0966c2a890f45003b093ff42dda2b702d0128002938d8573871

c3722fbc2357f3298b71197d7521a983ac79a6210826a38f9bb258e5e02c886c

67e5e3d0aff485ca2bf6f83151e1ecfae4a9b9335db657c72142ac9fd034250e

c7b789bf3c19ef3910cef02169c949a2e0a328e5449277113243449ec9a560a1

0925d447664fa88cf72383de0042014983d6526e85bb7a95e9c40f0fe45c8b5d

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

Campaign

RLMA-2024-088572024-08-embeds-RealtekHDAudioManagerRLUA-2026-00620

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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