MalwarePublished 10 Nov 2025

patria-liwet39-crottsekebon (npm) · Malicious Code

Affects patria-liwet39-crottsekebonSource GCVE Database

Malicious package : remove patria-liwet39-crottsekebon and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 07:27 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54141

What to do

Remove patria-liwet39-crottsekebon 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
npmpatria-liwet39-crottsekebon	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 patria-liwet39-crottsekebon 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, alter version numbers, and continuously republish variants, polluting the npm registry.

Impact

The malicious payload causes pollution of the npm registry by generating and publishing numerous derivative packages with randomized names. This can degrade the quality and trustworthiness of the npm ecosystem and potentially mislead developers relying on package metadata. There is no indication of direct exploitation or compromise of user systems beyond registry pollution.

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 preserve ecosystem integrity.

Summary

This threat involves a malicious npm package associated with the tea.xyz token reward campaign. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automate the creation and publication of derivative packages with randomized names to inflate developer reputation scores for token rewards. The malicious code modifies package.json by removing private flags and changing version numbers, enabling continuous republishing of variants. This behavior results in pollution of the npm package registry with numerous derivative packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 07:27 UTC

Technical details

Community reviews