node-test-repoRubyGems
Advisory published Updated
node-test-repo is a confirmed malicious RubyGems package (MAL-2026-20058) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in node-test-repo (RubyGems)
What this malware does
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for node-test-repo (version 1.0.1).
If you installed it — respond
Remove node-test-repo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If node-test-repo 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks node-test-repo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.