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

expo-router-on-railsnpm

Advisory published Updated

expo-router-on-rails is a confirmed malicious npm package (MAL-2025-191088) that steals credentials and exfiltrates sensitive data (malicious version 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in expo-router-on-rails (npm)

MAL-2025-191088
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall expo-router-on-rails

What this malware does

The package expo-router-on-rails 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

1 flagged
0.0.4

Indicators of compromise (SHA-256)

e850331b09e3722144062e90fa591195998f930b10434d0364c10de5f459a66e
b62a701d5d5e80ec78d223d1597706bae38d62711f3bb051ca966bfd48e57c1f
92bd7bcf264644e954c78205f555c4b45d42e4e628db37666799375a9a8777f5

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for expo-router-on-rails (version 0.0.4).

  2. If you installed it — respond

    expo-router-on-rails 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 expo-router-on-rails 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. expo-router-on-rails on npm has been identified as a malicious package (version 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-54vw-hpw5-ghw5

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks expo-router-on-rails-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
expo-router-on-rails (npm) malicious package — MAL-2025-191088 | O3 Security