amplitude-react-nativenpm
amplitude-react-native is a confirmed malicious npm package (MAL-2026-15525) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in amplitude-react-native (npm)
What this malware does
package.json declares a single dependency whose source is a bare HTTPS URL (https://repo.securityctrl.com/amplitude-react-native) rather than a registry version range, with no version pin and no integrity hash. The dependency key matches the package's own name, a dependency-confusion shape. On npm install, npm fetches whatever tarball that host currently returns and installs it, executing any lifecycle scripts contained in the fetched artifact. The shipped index.js is an inert stub, so the manifest itself is the entire published payload and the operator of repo.securityctrl.com controls code executed on installers' machines.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for amplitude-react-native (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amplitude-react-native across your stack and pipelines.
If you installed it — respond
Remove amplitude-react-native 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 amplitude-react-native 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 amplitude-react-native 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks amplitude-react-native-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.