Which versions of monkey-tags-ip are malicious?

Every published version of monkey-tags-ip on npm is considered malicious. Remove the package entirely.

How do I remediate monkey-tags-ip if I installed it?

monkey-tags-ip 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.

I already installed monkey-tags-ip — how do I know if it already compromised me?

If monkey-tags-ip 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.

How do I find monkey-tags-ip across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for monkey-tags-ip (all published versions).

Malicious package

monkey-tags-ipnpm

Advisory published Oct 13, 2026Updated Oct 14, 2026

monkey-tags-ip is a confirmed malicious npm package (MAL-2026-17875) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in monkey-tags-ip (npm)

MAL-2026-17875

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall monkey-tags-ip

What this malware does

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for monkey-tags-ip (all published versions).
If you installed it — respond
monkey-tags-ip 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 monkey-tags-ip 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. monkey-tags-ip on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

npmjs.com

Credits

SafeDep · finder

Detect & block this

O3 blocks monkey-tags-ip-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database