Which versions of react-dnd-14 are malicious?

The following npm versions of react-dnd-14 are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate react-dnd-14 if I installed it?

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

If react-dnd-14 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.

How do I find react-dnd-14 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-dnd-14 (version 99.9.1).

Malicious package

react-dnd-14npm

Advisory published Apr 30, 2026Updated Apr 30, 2026

react-dnd-14 is a confirmed malicious npm package (MAL-2026-3196) 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 react-dnd-14 (npm)

MAL-2026-3196

Immediate action

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

npm uninstall react-dnd-14

What this malware does

The package react-dnd-14 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'react-dnd-14' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

81d657eb3ca412fce2c80f37372316b6d00ddcb4bc8d74863cb43356d5a04c75

3fa1ee45bae09f53b3ad9f05448438098f0561c4b694a22360be9d4fa4e86b3d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for react-dnd-14 (version 99.9.1).
If you installed it — respond
Remove react-dnd-14 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 react-dnd-14 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. react-dnd-14 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.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks react-dnd-14-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