MalwarePublished 10 Nov 2025

qori-mieaceh34-riris (npm) · Malicious Code

Affects qori-mieaceh34-ririsSource GCVE Database

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

Data as of 6 Nov 2026, 18:52 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54503

What to do

Remove qori-mieaceh34-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
npmqori-mieaceh34-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 'qori-mieaceh34-riris' 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 change version numbers, enabling continuous republishing of variants to pollute the npm registry.

Impact

The malicious package manipulates the npm registry by flooding it with numerous derivative packages, which can degrade the quality and trustworthiness of the ecosystem. It may also mislead users and automated systems relying on package metadata. There is no direct evidence of exploitation in the wild or further payload delivery beyond registry pollution.

Defensive guidance

Users and maintainers should avoid installing or trusting packages associated with this campaign. Registry maintainers should consider removing these packages and implementing controls to detect and prevent automated republishing abuse.

Summary

This threat involves a malicious npm package that participates in the tea.xyz token reward campaign. The package includes scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automate the creation and publication of derivative packages with randomized names to artificially inflate developer reputation scores. The malicious code alters package.json by removing private flags and modifying version numbers, facilitating repeated republishing of variants. This activity results in registry pollution and potential abuse of the npm ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 18:52 UTC

Technical details

Community reviews