Which versions of confluent-docker-utils are malicious?

The following PyPI versions of confluent-docker-utils are flagged malicious: 0.0.89. Treat any of these as compromised.

How do I remediate confluent-docker-utils if I installed it?

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

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

Yes — confluent-docker-utils is associated with the RLMA-2024-08063, 2024-08-moti-analytics, RLUA-2026-00222 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 confluent-docker-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for confluent-docker-utils (version 0.0.89).

Malicious package

confluent-docker-utilsPyPI

Advisory published Aug 23, 2024Updated Mar 19, 2026

confluent-docker-utils is a confirmed malicious PyPI package (MAL-2024-9963) that steals credentials and exfiltrates sensitive data (malicious version 0.0.89). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in confluent-docker-utils (PyPI)

MAL-2024-9963

Immediate action

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

pip uninstall confluent-docker-utils

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

Indicators of compromise (SHA-256)

b3394ce5a4dd813415b7878e5dbf95887efcebe8d719f220d6eb80a489f49b53

fc88b843b5673be6ade9d44443eff573a21531af9e4f0deda0926bc80f6893fa

bc7d66b033c3d09c07ce3226cd534199a9f8cb2200a79035526192fb140b94d9

6ae62ef67fad328c54bb1172cc312f923c95d8042e009eeaed70d7095626c7f4

5334fcf3bb25c848429072ae1a6e255cf15e77de3358d064c28aff02b272a16f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for confluent-docker-utils (version 0.0.89).
If you installed it — respond
confluent-docker-utils 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 confluent-docker-utils 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. confluent-docker-utils on PyPI has been identified as a malicious package (version 0.0.89 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-080632024-08-moti-analyticsRLUA-2026-00222

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks confluent-docker-utils-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