Which versions of redis-di-processor are malicious?

The following PyPI versions of redis-di-processor are flagged malicious: 0.1.8. Treat any of these as compromised.

How do I remediate redis-di-processor if I installed it?

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

If redis-di-processor was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is redis-di-processor part of a known attack campaign?

Yes — redis-di-processor is associated with the RLMA-2024-09114, 2024-08-moti-analytics, RLUA-2026-00691 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 redis-di-processor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for redis-di-processor (version 0.1.8).

Malicious package

redis-di-processorPyPI

Advisory published Aug 23, 2024Updated Mar 19, 2026

redis-di-processor is a confirmed malicious PyPI package (MAL-2024-10152) that steals credentials and exfiltrates sensitive data (malicious version 0.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in redis-di-processor (PyPI)

MAL-2024-10152

Immediate action

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

pip uninstall redis-di-processor

What this malware does

The package is designed to exfiltrate basic data, like hostname and OS details, as well as collect information about the stacktrace it's imported from.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-08-moti-analytics

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

0.1.8

Indicators of compromise (SHA-256)

8807be7545a5c56b457c5b2b74d367132300b3876c053991c31c906fd9aabff0

33706cbb6110242aa641456e01c0b13fd33512ef13286633442b6828f5561205

d6942290379335757f0deff6d17e2490cd1b47f426b3f1fb533766ab804aa6cb

ebbd6b1490989148102e50444b4e5143aab85d6958579d5a9c18ffd40b0dcdbd

bb92be3bce441a380e0b950a99462cffd5edf1382e82af2fa76c18870667d632

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for redis-di-processor (version 0.1.8).
If you installed it — respond
redis-di-processor 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 redis-di-processor was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. redis-di-processor on PyPI has been identified as a malicious package (version 0.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-091142024-08-moti-analyticsRLUA-2026-00691

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks redis-di-processor-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

Explore

All malware advisories How O3 detects malware Vulnerability database