MalwarePublished 10 Nov 2025

joko-lutis2-sukiwir (npm) · Malicious Code

Affects joko-lutis2-sukiwirSource GCVE Database

Malicious package : remove joko-lutis2-sukiwir and rotate any secrets on hosts that installed it.

Data as of 10 Nov 2026, 18:13 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-57042

What to do

Remove joko-lutis2-sukiwir 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
npmjoko-lutis2-sukiwir	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 joko-lutis2-sukiwir is part of a malicious campaign linked to tea.xyz token rewards that floods the npm registry with autopublished derivative packages. These packages contain scripts that modify package metadata to remove privacy flags, alter version numbers, and generate randomized Indonesian-themed package names. This behavior aims to inflate developer reputation scores and pollute the npm ecosystem with numerous variants.

Impact

The primary impact is the pollution of the npm package registry with numerous derivative packages that can distort developer reputation metrics and potentially mislead users or automated systems relying on package metadata. There is no indication of direct exploitation or compromise of user systems, nor evidence of active exploitation in the wild.

Defensive guidance

Users and maintainers should avoid installing or trusting packages associated with this campaign. Registry maintainers should consider removing or blocking these autopublished derivative packages to prevent ecosystem pollution.

Summary

The malicious npm package joko-lutis2-sukiwir is involved in an automated campaign that uses autopublish scripts (such as auto.js and autopublish.js variants) to generate and publish numerous derivative packages with randomized names. The payload modifies package.json files by removing private flags and changing version numbers, enabling continuous republishing of variants. This activity is designed to manipulate developer reputation scores within the tea.xyz token reward system and results in pollution of the npm registry with many related packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 18:13 UTC

Technical details

Community reviews