Malicious code in @itsreduxtm/unpkg-xss-test (npm)
The npm package @itsreduxtm/unpkg-xss-test version 1.0.4 contained malicious code that executes on require/import, fetching a wordlist and conducting unauthorized reconnaissance scans against a third-party domain using the installer's IP address and identity.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed @itsreduxtm/unpkg-xss-test
- Ecosystems
- Attack vectors
- Affected entities
- @itsreduxtm/unpkg-xss-test · 1.0.4
The npm package @itsreduxtm/unpkg-xss-test (version 1.0.4) was found to contain malicious code in its main entry point (payload.js). The code executes immediately as an IIFE when the package is required or imported.\n\nUpon execution, the malicious code fetches a wordlist of Linux binary names from https://unpkg.com/@itsreduxtm/unpkg-xss-test@1.0.4/binlist.txt and then issues concurrent HEAD requests to https://entretienextremejb.ca/bin/ for each entry in the list. This reconnaissance activity is sourced from the installer's machine and IP address.\n\nThe package name and wordlist structure indicate this was designed as a browser XSS-delivered path-enumeration payload. However, when loaded in Node.js (where fetch is global in Node 18+), the installer unknowingly conducts the scan against the third-party target, weaponizing their identity for unauthorized reconnaissance. This exposes installers to potential abuse reports, IP blocklisting, and legal liability for unauthorized scanning activity.\n\nThe incident was identified by the OpenSSF malicious packages project and assigned identifier MAL-2026-13431.
Indicators of compromise
- Packages
- @itsreduxtm/unpkg-xss-test@1.0.4
- Domains
- unpkg.com
- entretienextremejb.ca
Remediation
- Immediately uninstall @itsreduxtm/unpkg-xss-test from all systems
- Remove the package from all dependency declarations (package.json, lock files)
- Audit systems for any suspicious outbound connections to entretienextremejb.ca
- Review IP reputation and consider notifying the target domain of the unauthorized scanning activity
- Use npm audit to check for any other malicious packages
- Consider implementing package verification and security scanning in your dependency management workflow
Sources
- GitHub Advisory GHSA-x3q4-9v45-gphv · GitHub Advisory Database
Cite this entry
"Malicious code in @itsreduxtm/unpkg-xss-test (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-itsreduxtm-unpkg-xss-test-npm-16htcd
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package