Malicious code in node-test-repo (RubyGems)
MAL-2026-20058
Published · Modified
Dependency scanning
Check whether node-test-repo 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 (39fc0f46ef530b718c8271a4a4495d4e766b227e821ff8ff949fd2b94062b0ae)
The gem declares an extension script in its gemspec, causing RubyGems to invoke it automatically during gem install. The script performs no native build work: it collects host identifiers (hostname, username, current working directory, home directory) and reads sensitive local files (/etc/passwd, /etc/hosts, /etc/resolv.conf), then opens a TLS TCPSocket to the hardcoded host e9okezgvlhxswlui5o94upb1ys4xsngc.oastify.com on port 443 and POSTs the collected JSON body to it. The destination is a Burp Collaborator out-of-band subdomain, not a publisher- or build-related endpoint, and the data read is unrelated to any compilation purpose.
Source: ossf-package-analysis (013b3a9afde1d4c01bf70bfa34b03fc9ca0f6a08dbb0a91db6fdccc481214468)
The OpenSSF Package Analysis project identified 'node-test-repo' @ 1.0.1 (rubygems) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes