MalwarePublished 10 Nov 2025

jaja-kripik11-sukiwir (npm) · Malicious Code

Affects jaja-kripik11-sukiwirSource GCVE Database

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

Data as of 10 Nov 2026, 18:07 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-56970

What to do

Remove jaja-kripik11-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
npmjaja-kripik11-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 jaja-kripik11-sukiwir 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, alters version numbers, and continuously republishes variants to pollute the npm registry.

Impact

The malicious payload enables continuous republishing of derivative packages, which pollutes the npm registry and inflates developer reputation scores fraudulently. This can degrade the quality and trustworthiness of the npm ecosystem and potentially mislead users relying on reputation metrics. 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 trusting packages associated with this campaign. Registry maintainers should consider removing or blocking these malicious packages to prevent ecosystem pollution.

Summary

This threat involves the jaja-kripik11-sukiwir npm package, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (such as auto.js and autopublish.js variants) that automate the creation and publication of numerous derivative packages with randomized names. The malicious code modifies package.json by removing private flags and changing version numbers to enable repeated publication. This behavior inflates developer reputation scores illegitimately and results in registry pollution by flooding npm with numerous variants.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews