intercom-react-native-example-e2e-testsRubyGems
Advisory published Updated
intercom-react-native-example-e2e-tests is a confirmed malicious RubyGems package (MAL-2026-18462) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in intercom-react-native-example-e2e-tests (RubyGems)
What this malware does
The gem declares ext/mkrf_conf.rb as an extension script, so it runs automatically on gem install. The script collects host reconnaissance data (hostname, username, current working directory, home directory) and reads sensitive local files (/etc/resolv.conf, /etc/passwd, /etc/hosts), serializes them as JSON, and transmits them over a TLS TCP socket to the hardcoded host 4diaipklp71i0by89eduyffr2i8dw3ks.oastify.com (a Burp Collaborator / OAST subdomain). A DNS lookup to the same host is issued as an out-of-band beacon, and the payload is tagged with an identifier (my_shoaib) to track successful landings. The package name mimics an unrelated JavaScript project (intercom-react-native), ships only an empty library module, and uses placeholder author metadata — consistent with a dependency-confusion / name-squat probe whose only functional behavior is the install-time exfiltration.
The OpenSSF Package Analysis project identified 'intercom-react-native-example-e2e-tests' @ 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
Credential / info stealerFind it
Search your lockfiles and build artifacts for intercom-react-native-example-e2e-tests (version 1.0.1).
If you installed it — respond
intercom-react-native-example-e2e-tests 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.
Did it already run?
If intercom-react-native-example-e2e-tests 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 intercom-react-native-example-e2e-tests-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.