Which versions of case-sensitive-paths are malicious?

The following npm versions of case-sensitive-paths are flagged malicious: 2.4.0, 2.4.1. Treat any of these as compromised.

How do I remediate case-sensitive-paths if I installed it?

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

If case-sensitive-paths 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 case-sensitive-paths part of a known attack campaign?

Yes — case-sensitive-paths is associated with the RLMA-2025-04940, RLUA-2025-05697 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 case-sensitive-paths across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for case-sensitive-paths (2 malicious versions).

Malicious package

case-sensitive-pathsnpm

Advisory published Aug 29, 2025Updated Dec 2, 2025

case-sensitive-paths is a confirmed malicious npm package (MAL-2025-41953) that executes malicious code on install (malicious versions 2.4.0, 2.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in case-sensitive-paths (npm)

MAL-2025-41953

Immediate action

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

npm uninstall case-sensitive-paths

What this malware does

The package case-sensitive-paths was found to contain malicious code.

Malicious versions

2 flagged

2.4.02.4.1

Indicators of compromise (SHA-256)

373bb06eccac0f822f0a5aef693b3df83c8e6b4c0d9aa045c6ae00042c5375ad

e466cc45eea5d544412380f09ce69f5628e94f9103f3b06bb1719db17c1af2da

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-04940RLUA-2025-05697

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks case-sensitive-paths-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