NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

react-native-emailnpm

Advisory published Updated

react-native-email is a confirmed malicious npm package (MAL-2025-190996) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.1, 2.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-native-email (npm)

MAL-2025-190996
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-native-email

What this malware does

The package react-native-email was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged
2.1.12.1.2

Indicators of compromise (SHA-256)

d4958583cd91bbe56c1fc60889b6baa9106b80cf2ad0edca1b8663eb841bc76d
685a2ceb0fc4b3de8462a07c55626285d47bbb72612a7feac2582a7dbfc2a606
65b2143504a158be854209736cc83efb98f19a171fddaa28f4ccc0214cb09eba
213d85eca55bf76d6d5ed1a0cd0df2dee658bd6628f8295ecf2457dc9f8f6222

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for react-native-email (2 malicious versions).

  2. If you installed it — respond

    react-native-email is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If react-native-email 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-native-email on npm has been identified as a malicious package (versions 2.1.1, 2.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-32m4-hxwx-rh9j

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks react-native-email-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

react-native-email (npm) malicious package — MAL-2025-190996 | O3 Security