MalwarePublished 10 Nov 2025

joni-serimuka97-ruro (npm) · Malicious Code

Affects joni-serimuka97-ruroSource GCVE Database

Malicious package : remove joni-serimuka97-ruro and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 09:01 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-52110

What to do

Remove joni-serimuka97-ruro 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
npmjoni-serimuka97-ruro	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 'joni-serimuka97-ruro' is part of a malicious campaign linked to the tea.xyz token reward scheme. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. These scripts modify package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. The intent is to inflate developer reputation scores and pollute the npm registry with malicious or spam packages.

Impact

The malicious payload enables continuous republishing of derivative packages, which pollutes the npm registry and artificially inflates developer reputation scores within the tea protocol token reward system. This can degrade the trustworthiness of the npm ecosystem and potentially expose users to malicious or untrusted code through these spam packages.

Defensive guidance

Mitigation involves avoiding use of the affected package and related variants. Registry maintainers and security teams should monitor and remove such autopublished malicious packages to maintain ecosystem integrity.

Summary

This threat involves the npm package 'joni-serimuka97-ruro', which is 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. These scripts alter package metadata by removing private flags and modifying version numbers to facilitate repeated publication. This behavior results in a flood of packages in the npm registry, aiming to manipulate developer reputation metrics and disrupt the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 09:01 UTC

Technical details

Community reviews