MalwarePublished 10 Nov 2025

gita-kue45-sluey (npm) · Malicious Code

Affects gita-kue45-slueySource GCVE Database

Malicious package : remove gita-kue45-sluey and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 08:53 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-51985

What to do

Remove gita-kue45-sluey 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
npmgita-kue45-sluey	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 gita-kue45-sluey npm package 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 Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants to pollute the npm registry.

Impact

The malicious payload can pollute the npm registry with numerous derivative packages, potentially misleading developers and automated systems relying on package metadata. It inflates developer reputation scores fraudulently within the tea protocol token reward system. While no direct exploitation or code execution impact is described, the registry pollution can degrade trust and complicate package management.

Defensive guidance

Users and maintainers should avoid installing or trusting packages related to this campaign. Registry maintainers should consider removing or blocking these autopublished variants to maintain registry integrity.

Summary

This threat involves the gita-kue45-sluey package on npm, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names. The malicious code alters package.json by removing private flags and modifying version numbers, facilitating repeated republishing of variants. This behavior aims to inflate developer reputation scores and flood the npm registry with numerous malicious or spam packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 08:53 UTC

Technical details

Community reviews