Which versions of xsilyxd are malicious?

The following PyPI versions of xsilyxd are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate xsilyxd if I installed it?

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

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

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

Malicious package

xsilyxdPyPI

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

MAL-2024-11750

Immediate action

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

pip uninstall xsilyxd

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

Indicators of compromise (SHA-256)

be389ff7d67d0123b8d56339c13a299f0f1c8c540e4b4e396a2facc66687278e

e70842332d72b0fe4ec398302a6dc0b5387198453045809893449c36c82bfc69

acb32201e238cb8cad93c54f19da257035f478ebebf6a5d7709ed787525b08b4

cb7ab2c8b2571d04e101a5416804cfb81ea36436908c047ea8d0daddf2412055

4849a843621b992e810e9bdebebbd51c7ddbfb46b478d5ded6cc2379f26a66e3

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

Campaign

RLMA-2024-112122024-08-embeds-RealtekHDAudioManagerRLUA-2026-00937

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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