roti4 (npm) · Malicious Code
Affects roti4Source GCVE Database
Malicious package : remove roti4 and rotate any secrets on hosts that installed it.
Data as of 12 Nov 2026, 20:05 UTC
Malicious package
Published to npm · OSV MAL-2025-181548
What to do
Remove roti4 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 |
|---|---|---|
| npmroti4 | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (da171d57526a228a3d43108b35fabfc5678236ef882064ba1994856b99be99fa) This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The malicious payload modifies package.json to remove private flags, changes version numbers, generates random Indonesian-themed package names (some variants are also in English), and continuously republishes variants to pollute the npm registry.