Which versions of redux-motion are malicious?

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

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

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

If redux-motion was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is redux-motion part of a known attack campaign?

Yes — redux-motion is associated with the RLMA-2025-06463, RLUA-2026-01539 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 redux-motion across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for redux-motion (version 1.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redux-motion across your stack and pipelines.

Malicious package

redux-motionnpm

Malicious code in redux-motion (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192857

Immediate action

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

npm uninstall redux-motion

What this malware does

The package redux-motion was found to contain malicious code.

Malicious versions

1 flagged

1.8.3

Indicators of compromise (SHA-256)

7a8d9935cf48f44d3b1df0cf1eace33f173ba2094bbba545640ae385a6cd82a9

8f2c75a688e2b889d1874da5d154e572f644290f2064d724629c36f7f396d43e

563bcc77dc7d0fb331bbe1ee285700c3892815944b0e66d3fd4bd16d92784f15

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for redux-motion (version 1.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redux-motion across your stack and pipelines.
If you installed it — respond
Remove redux-motion 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 redux-motion was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks redux-motion before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. redux-motion on npm has been identified as a malicious package (version 1.8.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06463RLUA-2026-01539

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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