Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

kkkaremnnpm

Malicious code in kkkaremn (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191969
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kkkaremn

What this malware does

The package kkkaremn was found to contain malicious code.

The OpenSSF Package Analysis project identified 'kkkaremn' @ 11.0.0 (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

3 flagged
6.0.09.0.011.0.0

Indicators of compromise (SHA-256)

38d12856c4db0126dfe51c098b1f21420abc032d85ddf07e3df4a6e4cb997b17
f3c03667184e3d719c08f1d45248aca18a92737f79234f902b8951883607e188
fb4aa0f8e8d709298eaf5820d8394091385138e9d2b2aec163c56343baba0a8e
8be05818c3e6f94f41c611af1a16f1a88489f457de3d8b98cc9c4441eee9e557
7cdd385021396db7dcc36db2e4fa8aabab09ebefbde60f07e11cb34ef0fcf2cf

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kkkaremn (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kkkaremn across your stack and pipelines.

  2. If you installed it — respond

    Remove kkkaremn 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.

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks kkkaremn 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. kkkaremn on npm has been identified as a malicious package (versions 6.0.0, 9.0.0, 11.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06392

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks kkkaremn-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.

kkkaremn (npm) malicious package — MAL-2025-191969 | O3 Security