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

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)

MAL-2026-20058
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall node-test-repo

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

1 flagged
1.0.1

Indicators of compromise (SHA-256)

013b3a9afde1d4c01bf70bfa34b03fc9ca0f6a08dbb0a91db6fdccc481214468
39fc0f46ef530b718c8271a4a4495d4e766b227e821ff8ff949fd2b94062b0ae

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for node-test-repo (version 1.0.1).

  2. 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.

  3. 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

No. node-test-repo on RubyGems has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022824

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.

Explore

node-test-repo (RubyGems) malicious package — MAL-2026-20058 | O3 Security