MalwarePublished 12 Nov 2025

kiut-acg-avecf (npm) · Malicious Code

Affects kiut-acg-avecfSource GCVE Database

Malicious package : remove kiut-acg-avecf and rotate any secrets on hosts that installed it.

Data as of 12 Nov 2026, 20:44 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-179739

What to do

Remove kiut-acg-avecf 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
npmkiut-acg-avecf	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 kiut-acg-avecf is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and generates random Indonesian-themed or English package names. This behavior results in continuous republishing of variants, polluting the npm registry.

Impact

This malicious package pollutes the npm registry by continuously publishing numerous derivative packages with randomized names, potentially misleading developers and automated systems relying on npm metadata. It manipulates package metadata to bypass private flags and inflate reputation scores, which can undermine trust in the npm ecosystem and token reward mechanisms. There is no indication of direct exploitation or compromise of user systems from this package.

Defensive guidance

Users and maintainers should avoid using the kiut-acg-avecf package and related variants. Registry maintainers and security teams should monitor and remove these malicious packages to prevent ecosystem pollution. Developers should verify package authenticity and metadata before use.

Summary

The kiut-acg-avecf npm package is involved in a token reward campaign flooding the npm registry with malicious packages. It uses autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) to automate the creation and publication of derivative packages with randomized names. The malicious code modifies package.json by removing private flags and changing version numbers, enabling repeated publication of variants. This activity aims to inflate developer reputation scores for the tea protocol token rewards and causes pollution of the npm package ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 20:44 UTC

Technical details

Community reviews