Which versions of @ably-forks/crypto-js are malicious?

The following npm versions of @ably-forks/crypto-js are flagged malicious: 3.999.0. Treat any of these as compromised.

How do I remediate @ably-forks/crypto-js if I installed it?

Remove @ably-forks/crypto-js 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 @ably-forks/crypto-js — how do I know if it already compromised me?

If @ably-forks/crypto-js 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 @ably-forks/crypto-js part of a known attack campaign?

Yes — @ably-forks/crypto-js is associated with the RLMA-2024-00004, RLUA-2024-05856, RLUA-2026-05791 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 @ably-forks/crypto-js across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ably-forks/crypto-js (version 3.999.0).

Malicious package

@ably-forks/crypto-jsnpm

Advisory published Jun 25, 2024Updated Sep 1, 2026

@ably-forks/crypto-js is a confirmed malicious npm package (MAL-2024-2033) that executes malicious code on install (malicious version 3.999.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ably-forks/crypto-js (npm)

MAL-2024-2033

Immediate action

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

npm uninstall @ably-forks/crypto-js

Malicious versions

1 flagged

3.999.0

Indicators of compromise (SHA-256)

a8df0ae4fdd0987d41395863dadb5a706feb1c18ff59b8f753241a18ee7aaf98

11dd5dad99b92652f72ffd891888e600b09f5ba66d7fa99cb87b64e31313e5c4

4179980dc8b4da1a0d6481754d4f6653b18a8310f7488ae8ebd63b37a1d1e669

134a93c7feda70af10f7bd6587890b8086541df596acb9cb775e969836bc52fe

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-00004RLUA-2024-05856RLUA-2026-05791

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @ably-forks/crypto-js-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