Which versions of motion-ani are malicious?

The following npm versions of motion-ani are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate motion-ani if I installed it?

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

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

Yes — motion-ani is associated with the RLMA-2026-05164, RLUA-2026-06332 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 motion-ani across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for motion-ani (version 2.3.5).

Malicious package

motion-aninpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

motion-ani is a confirmed malicious npm package (MAL-2026-7322) that executes malicious code on install (malicious version 2.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in motion-ani (npm)

MAL-2026-7322

Immediate action

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

npm uninstall motion-ani

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

f680ba64be97ecb14625b3434eec48b1f237315ab60b4f4ec0cfd066659a2abb

e2cd5ec1b3185cc8fc2e5e220ebdc990d923b005b8d9240c26ce62e208e10bdf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05164RLUA-2026-06332

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks motion-ani-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