Malicious code in uzair-rajput-new (npm)
The npm package 'uzair-rajput-new' contains malicious code concealed in its CommonJS (CJS) entrypoint. It reconstructs an AES-256-CBC decryption key by reading and XORing byte arrays from sibling files, then decrypts and executes an embedded payload at runtime. This behavior is hidden from static analysis and diverges from the benign ESM entrypoint, indicating deliberate obfuscation. Every require() call executes attacker-controlled code with the host process's privileges, posing a serious security risk.
AI Analysis
Technical Summary
The 'uzair-rajput-new' npm package masquerades as a color-gradient utility but embeds malicious code in its CJS main entrypoint. It reconstructs an AES-256-CBC key by XORing byte arrays from three sibling files with constants, concatenates the results, and derives a key via scryptSync with a fixed IV. This key decrypts a large base64-encoded payload, which is then executed dynamically using the Function constructor. The ESM entrypoint remains benign, indicating intentional concealment of malicious behavior in the CJS module. This design enables execution of attacker-controlled code with the privileges of the requiring process on every import.
Potential Impact
Any system or developer that installs and requires the affected versions of this package will execute attacker-controlled code with the same privileges as the Node.js process. This can lead to arbitrary code execution, potential system compromise, data theft, or further malware deployment. The malicious payload is concealed and dynamically decrypted, evading static detection methods.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately avoid using the affected versions of the 'uzair-rajput-new' package (=1.0.1, =1.1.0, =1.2.0, =1.3.0). Remove these versions from projects and replace them with trusted alternatives. Monitor dependency sources carefully and verify package integrity before installation. Check vendor advisories or trusted security databases for updates or patches.
Malicious code in uzair-rajput-new (npm)
Description
The npm package 'uzair-rajput-new' contains malicious code concealed in its CommonJS (CJS) entrypoint. It reconstructs an AES-256-CBC decryption key by reading and XORing byte arrays from sibling files, then decrypts and executes an embedded payload at runtime. This behavior is hidden from static analysis and diverges from the benign ESM entrypoint, indicating deliberate obfuscation. Every require() call executes attacker-controlled code with the host process's privileges, posing a serious security risk.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'uzair-rajput-new' npm package masquerades as a color-gradient utility but embeds malicious code in its CJS main entrypoint. It reconstructs an AES-256-CBC key by XORing byte arrays from three sibling files with constants, concatenates the results, and derives a key via scryptSync with a fixed IV. This key decrypts a large base64-encoded payload, which is then executed dynamically using the Function constructor. The ESM entrypoint remains benign, indicating intentional concealment of malicious behavior in the CJS module. This design enables execution of attacker-controlled code with the privileges of the requiring process on every import.
Potential Impact
Any system or developer that installs and requires the affected versions of this package will execute attacker-controlled code with the same privileges as the Node.js process. This can lead to arbitrary code execution, potential system compromise, data theft, or further malware deployment. The malicious payload is concealed and dynamically decrypted, evading static detection methods.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately avoid using the affected versions of the 'uzair-rajput-new' package (=1.0.1, =1.1.0, =1.2.0, =1.3.0). Remove these versions from projects and replace them with trusted alternatives. Monitor dependency sources carefully and verify package integrity before installation. Check vendor advisories or trusted security databases for updates or patches.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13360
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7573b5bf8831d539d93ace
Added to database: 08/07/2026, 05:57:09 UTC
Last enriched: 08/07/2026, 07:43:01 UTC
Last updated: 08/07/2026, 07:43:01 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.