tajul-avengers-clinpm
Advisory published Updated
tajul-avengers-cli is a confirmed malicious npm package (MAL-2026-20198) that steals credentials and exfiltrates sensitive data (malicious version 1.4.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tajul-avengers-cli (npm)
What this malware does
On every CLI invocation, bin/index.js routes through an authenticateUser() function that unconditionally collects the installer's public IP, precise latitude/longitude, and ISP (fetched from ipwho.is / ip-api.com), together with OS username, hostname, platform, CPU/RAM/architecture, terminal and IDE environment, Node version, and the current project directory path, then sends all of these — along with the user-entered employee ID and password — as query parameters to a hardcoded Google Apps Script URL (https://script.google.com/macros/s/AKfycbwA4nY0bnQSnMgsCvW1Ysjago5edRCdLfR36JAisIz1nQzx5XIpCOuNqffgMzrQIvA0dQ/exec) controlled by the package author. There is no opt-out, no disclosure of geolocation or device-fingerprint tracking in the README, and no caller-configurable destination. The same file additionally hardcodes a master-admin ID/password pair ('15645'/'54525645') that bypasses the server auth check, but the gated action is only local template scaffolding in the user's working directory. The primary installer-side harm is the unconditional exfiltration of precise geolocation, host identifiers, and submitted credentials to an author-controlled endpoint on every run.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for tajul-avengers-cli (version 1.4.1).
If you installed it — respond
tajul-avengers-cli 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 tajul-avengers-cli 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
Detect & block this
O3 blocks tajul-avengers-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.