Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in intercom-react-native-example-e2e-tests (RubyGems)

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • RubyGems intercom-react-native-example-e2e-tests

    Affected
    >= 1.0.1, <= 1.0.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (57e084aff68cdd6201d55d3375bbc29f6e741553d4ac083f910fc38e110ef3d1) 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-18462

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: mal-2026-18462

Advisory: Malicious code in intercom-react-native-example-e2e-tests (RubyGems)
IDs: mal-2026-18462
Record: https://patchnext.com/advisories/mal-2026-18462 (revision 1, source checked 3 Nov 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems intercom-react-native-example-e2e-tests: affected >= 1.0.1, <= 1.0.1

## Suggested inspection (read-only)
- RubyGems intercom-react-native-example-e2e-tests: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on intercom-react-native-example-e2e-tests.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18462 (OSV record MAL-2026-18462 lists affected ranges: RubyGems intercom-react-native-example-e2e-tests >=1.0.1 <=1.0.1)

Commands are suggestions: review each one before running it.

Loading voting…