Which versions of artindex are malicious?

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

How do I remediate artindex if I installed it?

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

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

Yes — artindex is associated with the RLMA-2024-07830, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00078 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 artindex 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 artindex (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 artindex across your stack and pipelines.

Malicious package

artindexPyPI

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

MAL-2024-9943

Immediate action

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

pip uninstall artindex

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)

43e28265c681527f9fce301e8996e038f3a92428bc79a904aaca45d5c9a76aae

bed327e8caef3b60190d483d0632f4ffe8ff26e799409916ac92eff6d0af43bc

3f19c3c0f0a7d0edd2a53f7c3879706561e0e7d4596b11e9eebbb1d896e90a46

733a00a1f3e74a670bf1afdff9384072ddc0a0f3dc11b16fbdc1d6419028e873

78b0816ef009c11859a182f87083c9591ba7c286bd5bc8dbcaab7a403dbb5b10

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 artindex (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 artindex across your stack and pipelines.
If you installed it — respond
artindex 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 artindex 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 artindex 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. artindex 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-078302024-08-embeds-RealtekHDAudioManagerRLUA-2026-00078

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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