uzair-rajput-newnpm
uzair-rajput-new is a confirmed malicious npm package (MAL-2026-13360) that executes malicious code on install (malicious versions 1.0.1, 1.1.0, 1.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in uzair-rajput-new (npm)
What this malware does
The package is published as a chalk/tinygradient color-gradient wrapper, and its ESM entrypoint dist/index.js matches that description. The CJS main dist/index.cjs diverges: at module load it reconstructs an AES-256-CBC key by reading byte arrays from sibling files dist/_a.cjs, dist/_b.cjs, and dist/_c.cjs, XORing them with the constants 17, 91, and 53, concatenating the results, and passing that through scryptSync alongside a hex IV literal. The derived key is used with createDecipheriv('aes-256-cbc',...) to decrypt a large embedded base64 blob, and the resulting source is executed via new Function('module','exports','require','__dirname','__filename', _x)(...). The stated purpose (color gradients) has no legitimate need for an encrypted payload with a key split across three sibling files and evaluated at require-time; the split-key + AES + new Function pattern conceals the payload from static inspection, and the divergence between the benign ESM twin and the obfuscated CJS entrypoint indicates deliberate concealment. Every require() of this package on the installer's host runs attacker-controlled code with the process's privileges.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for uzair-rajput-new (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uzair-rajput-new across your stack and pipelines.
If you installed it — respond
Remove uzair-rajput-new from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If uzair-rajput-new was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks uzair-rajput-new before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks uzair-rajput-new-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.