MalwarePublished 10 Nov 2025

dono-moci4-riris (npm) · Malicious Code

Affects dono-moci4-ririsSource GCVE Database

Malicious package : remove dono-moci4-riris and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 08:03 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-51609

What to do

Remove dono-moci4-riris 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
npmdono-moci4-riris	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 dono-moci4-riris was identified as containing malicious code linked to a large-scale spam campaign associated with the tea.xyz token reward system. This campaign involved flooding the npm registry with over 15,000 spam packages that include autopublish scripts to automatically generate and publish derivative packages with randomized names. The malicious payload manipulates package metadata to remove privacy flags, alter version numbers, and create Indonesian-themed package names, continuously republishing variants to pollute the npm ecosystem.

Impact

This malicious package contributes to ecosystem pollution by flooding the npm registry with spam packages, which can degrade the quality and trustworthiness of the npm ecosystem. It also manipulates package metadata to bypass privacy settings and inflate developer reputation scores fraudulently. 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 depending on the dono-moci4-riris package and other related spam packages from the tea.xyz campaign. Registry maintainers should continue to identify and remove such spam packages to preserve ecosystem integrity.

Summary

The dono-moci4-riris package is part of a widespread npm spam campaign tied to the tea.xyz token reward initiative. It contains autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names. The malicious code modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. This behavior inflates developer reputation scores illegitimately and pollutes the npm registry with spam packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 08:03 UTC

Technical details

Community reviews