Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

omniauth-recharge-rails-examplenpm

Advisory published Updated

omniauth-recharge-rails-example is a confirmed malicious npm package (MAL-2026-14526) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in omniauth-recharge-rails-example (npm)

MAL-2026-14526
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall omniauth-recharge-rails-example

What this malware does

The package's package.json declares a preinstall lifecycle script that runs wget against a hardcoded webhook.site URL (https://webhook.site/26e65e9b-fd9c-4f3f-beb3-063309f4d7d9/) with query parameters carrying $(whoami), $(pwd), and $(hostname) from the installer's machine. The request fires automatically on npm install, transmitting the installer's username, working directory path, and hostname to a third-party collector controlled by whoever provisioned the webhook token. This is the canonical dependency-confusion / namespace-squat beacon pattern used to prove reachability into an internal network by leaking host identity.

The OpenSSF Package Analysis project identified 'omniauth-recharge-rails-example' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

915a378563ab8481e64d0a202e4d037a722361eae5263812c7648dce30cc557e
27ec72eac9d0bae686eddce65991c912a23c97621648e3316cd05188038d17d7

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for omniauth-recharge-rails-example (version 1.0.0).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-018745

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks omniauth-recharge-rails-example-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
omniauth-recharge-rails-example (npm) malicious package — MAL-2026-14526 | O3 Security