Which versions of didirce are malicious?

The following npm versions of didirce are flagged malicious: 1.2.9, 1.3.0. Treat any of these as compromised.

How do I remediate didirce if I installed it?

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

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

Yes — didirce is associated with the RLMA-2025-05344, RLUA-2025-05766 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 didirce across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for didirce (2 malicious versions).

Malicious package

didircenpm

Advisory published Oct 17, 2025Updated Dec 2, 2025

didirce is a confirmed malicious npm package (MAL-2025-48490) that executes malicious code on install (malicious versions 1.2.9, 1.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in didirce (npm)

MAL-2025-48490

Immediate action

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

npm uninstall didirce

What this malware does

The package didirce was found to contain malicious code.

Malicious versions

2 flagged

1.2.91.3.0

Indicators of compromise (SHA-256)

e5fe720f029ca74514242f6b9f95af1cf1e4d89b7f569c29d5e1bade3351189b

1bef524514b540a27acae61ed75d0920b56df366c35ca9b097de955d43fefe93

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05344RLUA-2025-05766

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks didirce-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