Which versions of confluent-kafka-javascript are malicious?

The following npm versions of confluent-kafka-javascript are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate confluent-kafka-javascript if I installed it?

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

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

Yes — confluent-kafka-javascript is associated with the GHSA-j28m-58xp-3wgh, IN-MAL-2026-008142 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-kafka-javascript 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 confluent-kafka-javascript (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 confluent-kafka-javascript across your stack and pipelines.

Malicious package

confluent-kafka-javascriptnpm

confluent-kafka-javascript is a confirmed malicious npm package (MAL-2026-6682) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in confluent-kafka-javascript (npm)

MAL-2026-6682

Immediate action

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

npm uninstall confluent-kafka-javascript

What this malware does

Analysis of this package version produced no static indicator and no traced behavioral findings. The tarball does not exhibit lifecycle-script droppers, credential reads, environment scraping, hardcoded attacker network destinations, or other installer-harm patterns. With no concrete evidence of exfiltration, install-time remote code execution, silent-relay, or backdoor mechanisms in this version's content, there is no basis to block or escalate.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6eff5dfc962c2ae45ca37fa55f80a36203cf198cef04726258100accadc25378

e20f9433c5da4c3ee143c33ec2a876e07ff01aa1188d0efa783858bcd0903d3c

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 confluent-kafka-javascript (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 confluent-kafka-javascript across your stack and pipelines.
If you installed it — respond
confluent-kafka-javascript 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-kafka-javascript 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 confluent-kafka-javascript 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. confluent-kafka-javascript on npm 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

GHSA-j28m-58xp-3wghIN-MAL-2026-008142

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks confluent-kafka-javascript-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