Which versions of keythereum-utils are malicious?

The following npm versions of keythereum-utils are flagged malicious: 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.7. Treat any of these as compromised.

How do I remediate keythereum-utils if I installed it?

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

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

Yes — keythereum-utils is associated with the GHSA-fxwg-c72r-c7jf, RLMA-2025-03900, RLUA-2025-06390 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 keythereum-utils 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 keythereum-utils (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging keythereum-utils across your stack and pipelines.

Malicious package

keythereum-utilsnpm

keythereum-utils is a confirmed malicious npm package (MAL-2025-5504) that executes malicious code on install (malicious versions 1.2.1, 1.2.2, 1.2.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in keythereum-utils (npm)

MAL-2025-5504

Immediate action

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

npm uninstall keythereum-utils

What this malware does

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

6 flagged

1.2.11.2.21.2.31.2.41.2.51.2.7

Indicators of compromise (SHA-256)

e190a6b75c720484c00bc747f1ea989c80b20733327b6a0ff26d29538aa471f2

7a9fbe82ae1f7b38894b6ace341a87fb68bdaf0576de40cfdd3d504ae83ceb66

931cc84b4c5617348c7fe30649287c73edf56afa949544de36805ba310f56cc3

cffe3eff2d56554f567bbe97a919462c71f1b0f96c13f3e6a5f2735de0c1b42f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for keythereum-utils (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging keythereum-utils across your stack and pipelines.
If you installed it — respond
Remove keythereum-utils 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 keythereum-utils 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 keythereum-utils 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. keythereum-utils on npm has been identified as a malicious package (versions 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fxwg-c72r-c7jfRLMA-2025-03900RLUA-2025-06390

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks keythereum-utils-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