Which versions of ke-moma are malicious?

The following npm versions of ke-moma are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ke-moma if I installed it?

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

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

Yes — ke-moma is associated with the RLMA-2025-06388 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 ke-moma across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ke-moma (version 1.0.0).

Malicious package

ke-momanpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

ke-moma is a confirmed malicious npm package (MAL-2025-192821) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ke-moma (npm)

MAL-2025-192821

Immediate action

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

npm uninstall ke-moma

What this malware does

The package ke-moma was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2f7621ca88c2775457fb1af17552940d96adf1aeb266681b8ef29843976cd0c0

d055ad9b9b61ad21df044f2fa8e31497087dc013102277db91bd478f412333ef

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06388

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ke-moma-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