Which versions of motiondnb are malicious?

The following npm versions of motiondnb are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate motiondnb if I installed it?

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

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

Yes — motiondnb is associated with the GHSA-278r-46x5-pfjm, RLMA-2026-05575, RLUA-2026-06334 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 motiondnb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for motiondnb (version 99.9.1).

Malicious package

motiondnbnpm

Advisory published Jul 10, 2026Updated Sep 1, 2026

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

Malicious code in motiondnb (npm)

MAL-2026-10145

Immediate action

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

npm uninstall motiondnb

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

11d8d84a54d776c1b4d6b53bdb39c8b181d9bfde03da128c7b3f58d6fb631284

cf115ee9a93c04d86b97353e854a4b50ad8ab12524691caed6c56dceb07b392c

08eba8f82bdff8c7c6b7b73a20ecbcef724df651de20b4c2380ddcef34d4c8cc

Detection & response playbook

Malicious package

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

Campaign

GHSA-278r-46x5-pfjmRLMA-2026-05575RLUA-2026-06334

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks motiondnb-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