Which versions of larpexodus are malicious?

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

How do I remediate larpexodus if I installed it?

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

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

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

Malicious package

larpexodusPyPI

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

MAL-2024-11622

Immediate action

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

pip uninstall larpexodus

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)

a3629568af0b8286902a1656f5b51b67f98dccf528db4bbd5a094063f92b774d

48f436064981bb8dce32933dc73475abf94985a816804b0a4571f0eec1b1219a

5b391a50d47eceb41e0f102a5825b7e68d35a2c950ecc91f32c2b48e890792b9

3ee0c42ec3dd141d7ce82ea3e8212e82c03e06599ad69f1547e9df105bc08290

c1d10ce79594d0d970c7c48f9e5265d38367594f9be95fd2458fdb8c2e853e01

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 larpexodus (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging larpexodus across your stack and pipelines.
If you installed it — respond
larpexodus 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 larpexodus 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 larpexodus 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. larpexodus 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-110762024-08-embeds-RealtekHDAudioManagerRLUA-2026-00463

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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