MalwarePublished 10 Nov 2025

mahesa-jamblang24-sluey (npm) · Malicious Code

Affects mahesa-jamblang24-slueySource GCVE Database

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

Data as of 5 Nov 2026, 11:50 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-53294

What to do

Remove mahesa-jamblang24-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
npmmahesa-jamblang24-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 npm package 'mahesa-jamblang24-sluey' 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 leads to pollution of the npm registry with numerous derivative packages, which can degrade the trustworthiness of the ecosystem. It may also artificially inflate developer reputation scores within the tea protocol token reward system. There is no indication of direct exploitation or compromise of user systems from this package alone.

Defensive guidance

Users and maintainers should avoid installing or depending on packages linked to this campaign. Registry maintainers should consider removing these packages and monitoring for similar autopublish scripts to prevent ecosystem pollution.

Summary

This threat involves a malicious npm package 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 to facilitate repeated republishing. This activity aims to inflate developer reputation scores and flood the npm registry with numerous variants, potentially undermining the integrity of the package ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 11:50 UTC

Technical details

Community reviews