Malicious code in rechargeapps (RubyGems)
MAL-2026-20137
Published · Modified
Dependency scanning
Check whether rechargeapps is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (e3adc43a1ce04c304a176f8f8861b89b99f7df1b0a4f940bdcf1274f24ff157f)
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, devops@example.com), 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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes