Which versions of ke-moma2 are malicious?

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

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

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

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

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

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

Malicious package

ke-moma2npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

ke-moma2 is a confirmed malicious npm package (MAL-2025-192822) 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-moma2 (npm)

MAL-2025-192822

Immediate action

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

npm uninstall ke-moma2

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f361b6de31f77a588b93c2368880aeeb1a389aa171e51bd36ba53fd3689f7554

9d8703622faa5dfbd1a83aa416844cfa365266b95b4b4e2e99b597e60b26d578

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ke-moma2 (version 1.0.0).
If you installed it — respond
Remove ke-moma2 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-moma2 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-moma2 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-06389

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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