Which versions of curse-allies-module are malicious?

The following npm versions of curse-allies-module are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate curse-allies-module if I installed it?

curse-allies-module establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed curse-allies-module — how do I know if it already compromised me?

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

Yes — curse-allies-module is associated with the IN-MAL-2026-022765 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 curse-allies-module across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for curse-allies-module (version 1.0.0).

Malicious package

curse-allies-modulenpm

Advisory published Nov 13, 2026Updated Nov 13, 2026

curse-allies-module is a confirmed malicious npm package (MAL-2026-19223) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in curse-allies-module (npm)

MAL-2026-19223

Immediate action

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

npm uninstall curse-allies-module

What this malware does

On npm install, the package runs a postinstall lifecycle script (node probe.cjs) that issues an HTTPS POST to a hardcoded webhook.site collector URL (https://webhook.site/a4bf0f9f-6d96-46e6-80ac-b76a5329f481) with the marker string CURSE_DEPENDENT_REMOTE_INSTALL_PROBE. The beacon fires unconditionally at install time with no configuration or opt-out, signaling to a third-party collector that the package resolved and executed inside the installer's environment. This is the canonical dependency-confusion / reconnaissance canary shape: the attacker learns that a given name resolves on the target's internal build infrastructure, enabling follow-on targeted attacks against environments where the name was expected to resolve privately.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

15e9740e7be22c3d68a1784e48d3e87414347b5e5697397ef0d8ab2295619962

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for curse-allies-module (version 1.0.0).
If you installed it — respond
curse-allies-module establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If curse-allies-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. curse-allies-module on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022765

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks curse-allies-module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database