Skip to content

← Actionable
Unratedamended

Malicious code in monkey-tags-ip (npm)

GHSA-97j9-4wmq-rgfv

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.

Affected packages

  • npm monkey-tags-ip

    Affected
    every version
    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.

npm user 'conx3993' published this package in a dependency confusion campaign. It squats a name that looks like an internal package and uses version 53.4.1 so misconfigured resolvers pick it over the real one. Version 0.0.0-stage is an empty placeholder. A 'preinstall' hook runs 'ip.js', which poses as an IP geolocation helper. On install it sends an HTTPS GET to attacker-controlled host realwbx.com (/ip?f=json) with a hard-coded 'Authorization' value ('Bearer xHlT6gllTfGbKgdivAKTzWKxrILWlNlv') unique to this package, then discards the response. The token tells the operator which internal package name the victim installed, and the request reveals the victim's public egress IP. --- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (156e7f5f47312f5f7cd43584abd568920027ab28b6e98f2b65f22cd6a2c4141f) monkey-tags-ip@53.4.1 is a stub package whose entire behavior is an install-time beacon. The `preinstall` script executes `node ip.js`, which unconditionally…

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

    Amended from osv record MAL-2026-17875

  2. Revision 1 · created ·

    Published from osv record MAL-2026-17875

Agent brief

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

# Patch Next advisory brief: GHSA-97j9-4wmq-rgfv

Advisory: Malicious code in monkey-tags-ip (npm)
IDs: GHSA-97j9-4wmq-rgfv
Record: https://patchnext.com/advisories/mal-2026-17875 (revision 2, source checked 4 Nov 2026, 06:00 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
- npm monkey-tags-ip: affected every version

## Suggested inspection (read-only)
- `npm ls monkey-tags-ip --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 monkey-tags-ip.
- 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-17875 (OSV record MAL-2026-17875 lists affected ranges: npm monkey-tags-ip >=0)

Commands are suggestions: review each one before running it.

Loading voting…