Which versions of cursed-module are malicious?

The following npm versions of cursed-module are flagged malicious: 1.23.500, 2.14.800, 2.14.801, 3.45.101. Treat any of these as compromised.

How do I remediate cursed-module if I installed it?

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

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

Yes — cursed-module is associated with the RLMA-2026-01735 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 cursed-module across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cursed-module (4 malicious versions).

Malicious package

cursed-modulenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

cursed-module is a confirmed malicious npm package (MAL-2026-2348) that executes malicious code on install (malicious versions 1.23.500, 2.14.800, 2.14.801…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cursed-module (npm)

MAL-2026-2348

Immediate action

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

npm uninstall cursed-module

What this malware does

The package cursed-module was found to contain malicious code.

Malicious versions

4 flagged

1.23.5002.14.8002.14.8013.45.101

Indicators of compromise (SHA-256)

1664ad5dd35a798a58c0f2d90f8d71fd0202d7be936e372fcf7ca3af7b4ee758

8f33e4c756bc2b6484a9c8ddc7510e2b7e3dfee1ba963a77d610e61c2c897821

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01735

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cursed-module-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