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

rechargeappsRubyGems

Advisory published Updated

rechargeapps is a confirmed malicious RubyGems package (MAL-2026-20137) that steals credentials and exfiltrates sensitive data (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rechargeapps (RubyGems)

MAL-2026-20137
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall rechargeapps

What this malware does

The gem's extension build script (run during gem install) reads /proc/self/environ (falling back to ENV) and POSTs it base64-encoded to the hardcoded endpoint https://webhook.site/5f869495-8820-4e0a-b759-8c61e0b0d6ce, with a second curl-based repost of /proc/self/environ to the same URL. The library entry point additionally performs a top-level Net::HTTP POST of the full process environment (ENV.to_a, base64-packed) along with pid and hostname to the same webhook.site URL every time require 'rechargeapps' is evaluated. The build Makefile is a no-op stub and the module body is otherwise empty, so these two network callbacks are the gem's sole behavior. The published artifact is version 999.0.0 with placeholder metadata (homepage example.com, [email protected]), consistent with a dependency-confusion squat targeting an internal name 'rechargeapps' to capture CI and build-host environment variables (tokens, cloud keys, registry credentials) at install and load time.

Malicious versions

1 flagged
999.0.0

Indicators of compromise (SHA-256)

e3adc43a1ce04c304a176f8f8861b89b99f7df1b0a4f940bdcf1274f24ff157f

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for rechargeapps (version 999.0.0).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-022827

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rechargeapps-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

rechargeapps (RubyGems) malicious package — MAL-2026-20137 | O3 Security