Which versions of react-datepicker-next are malicious?

The following npm versions of react-datepicker-next are flagged malicious: 93.98.5. Treat any of these as compromised.

How do I remediate react-datepicker-next if I installed it?

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

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

Yes — react-datepicker-next is associated with the RLMA-2026-05256, RLUA-2026-06414 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 react-datepicker-next across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-datepicker-next (version 93.98.5).

Malicious package

react-datepicker-nextnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

react-datepicker-next is a confirmed malicious npm package (MAL-2026-7365) that executes malicious code on install (malicious version 93.98.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-datepicker-next (npm)

MAL-2026-7365

Immediate action

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

npm uninstall react-datepicker-next

Malicious versions

1 flagged

93.98.5

Indicators of compromise (SHA-256)

58a0517cc1de9c6ff750e42d3b222bd93dfcb6f8fd93df43947bf176b5d8b611

414ceae9a26f5593780d296129cfa0b1a3d4a0d2793502b87107f94d73b1daff

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05256RLUA-2026-06414

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks react-datepicker-next-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