Which versions of csec-crypto-utils are malicious?

The following npm versions of csec-crypto-utils are flagged malicious: 4.2.1. Treat any of these as compromised.

How do I remediate csec-crypto-utils if I installed it?

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

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

Yes — csec-crypto-utils is associated with the RLMA-2026-05036, RLUA-2026-06171 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 csec-crypto-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for csec-crypto-utils (version 4.2.1).

Malicious package

csec-crypto-utilsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

csec-crypto-utils is a confirmed malicious npm package (MAL-2026-7248) that executes malicious code on install (malicious version 4.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in csec-crypto-utils (npm)

MAL-2026-7248

Immediate action

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

npm uninstall csec-crypto-utils

Malicious versions

1 flagged

4.2.1

Indicators of compromise (SHA-256)

7c0a21e1ba022a7fe51887078d1d74012b637afa87e845ba377bbd45d117615f

3753396bb063ff5654a8c58379e120b91cd4138409821ffd24cfa1d2736f325f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05036RLUA-2026-06171

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks csec-crypto-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