alaaddindar (npm) · Malicious Code
Affects alaaddindarSource GCVE Database
Malicious package : remove alaaddindar and rotate any secrets on hosts that installed it.
Data as of 20 Nov 2026, 19:59 UTC
Malicious package
Published to npm · OSV MAL-2025-170778
What to do
Remove alaaddindar from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmalaaddindar | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'alaaddindar' version 1.0.0 is part of a malicious campaign flooding the npm registry with autopublish scripts that generate and publish derivative packages with randomized names. This activity aims to inflate developer reputation scores for the tea.xyz token reward campaign. The malicious payload modifies package.json files to remove private flags, changes version numbers, and continuously republishes variants, polluting the npm ecosystem. Systems with this package installed should be considered fully compromised, with all stored secrets and keys requiring immediate rotation.