What does the kmeet malware do?

The package kmeet was found to contain malicious code. The OpenSSF Package Analysis project identified 'kmeet' @ 77.7.7 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of kmeet are malicious?

The following npm versions of kmeet are flagged malicious: 77.7.7. Treat any of these as compromised.

How do I remediate kmeet if I installed it?

Remove kmeet from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed kmeet — how do I know if it already compromised me?

If kmeet 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.

How do I find kmeet across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kmeet (version 77.7.7).

Malicious package

kmeetnpm

Advisory published Jan 7, 2026Updated Jan 8, 2026

kmeet is a confirmed malicious npm package (MAL-2026-125) that executes malicious code on install (malicious version 77.7.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kmeet (npm)

MAL-2026-125

Immediate action

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

npm uninstall kmeet

What this malware does

The package kmeet was found to contain malicious code.

The OpenSSF Package Analysis project identified 'kmeet' @ 77.7.7 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

77.7.7

Indicators of compromise (SHA-256)

6d1b109e5fb22408addfc93b1e1c172970312ae04f4b194bf5156abb941742ff

0007533264dfce09777a32ebaa374e6f78f7af5ea6d8df57d7a92ce22590a09e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kmeet (version 77.7.7).
If you installed it — respond
Remove kmeet from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If kmeet 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. kmeet on npm has been identified as a malicious package (version 77.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks kmeet-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database