MalwarePublished 10 Nov 2025

okta-kemplang15-ruro (npm) · Malicious Code

Affects okta-kemplang15-ruroSource GCVE Database

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

Data as of 5 Nov 2026, 08:42 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-53925

What to do

Remove okta-kemplang15-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
npmokta-kemplang15-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 okta-kemplang15-ruro npm package 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, change version numbers, and continuously republish variants, polluting the npm registry.

Impact

The malicious payload enables continuous automated publication of derivative npm packages, which pollutes the npm registry with numerous variants. This can undermine the integrity of the npm ecosystem, potentially mislead developers relying on package metadata, and inflate reputation scores fraudulently. There is no direct evidence of exploitation in the wild or further payload delivery beyond registry pollution.

Defensive guidance

Users should avoid installing the okta-kemplang15-ruro package and related variants. Registry maintainers and security teams should monitor and remove such malicious packages from npm to prevent ecosystem pollution.

Summary

This threat involves the okta-kemplang15-ruro package, which is associated with the tea.xyz token reward campaign flooding the npm ecosystem. The package includes autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names to inflate developer reputation scores for token rewards. The malicious code alters package.json by removing private flags and changing version numbers, enabling continuous republishing of variants. This activity results in npm registry pollution and potential trust issues with affected packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews