MalwarePublished 10 Nov 2025

siska-tiwul97-wekto (npm) · Malicious Code

Affects siska-tiwul97-wektoSource GCVE Database

Malicious package : remove siska-tiwul97-wekto and rotate any secrets on hosts that installed it.

Data as of 7 Nov 2026, 17:16 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54949

What to do

Remove siska-tiwul97-wekto 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
npmsiska-tiwul97-wekto	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 siska-tiwul97-wekto 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 changes version numbers to enable continuous republishing, polluting the npm registry.

Impact

The malicious package pollutes the npm registry by continuously 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 direct evidence of exploitation or compromise beyond registry pollution and reputation inflation.

Defensive guidance

Users should avoid installing packages associated with the tea.xyz token reward campaign and verify package authenticity before use. Registry maintainers and npm administrators should monitor and remove such malicious packages to protect the ecosystem.

Summary

This threat involves a malicious npm package, siska-tiwul97-wekto, 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 derivative packages with randomized names. These scripts alter package.json by removing private flags and incrementing version numbers, facilitating repeated republishing. The objective is to inflate developer reputation scores for tea protocol token rewards and to flood the npm registry with numerous variants, thereby polluting the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2026, 17:16 UTC

Technical details

Community reviews