Malicious Code Injection in putri-wajit29-ruro Package - npm Vulnerability

putri-wajit29-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107557: Malicious code in putri-wajit29-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The putri-wajit29-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. This package has been identified as malicious due to its ability to modify package metadata and republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in the putri-wajit29-ruro package stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall putri-wajit29-ruro

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can avoid using the putri-wajit29-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The putri-wajit29-ruro package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities using tools like Vulert to maintain the security and integrity of your applications.

See every vulnerability recorded for putri-wajit29-ruro →

Share this vulnerability

FAQ

The putri-wajit29-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies package metadata and repopulates the npm registry with potentially harmful packages.

If you have installed the putri-wajit29-ruro package, you should uninstall it immediately using npm uninstall putri-wajit29-ruro and check for any dependencies that may be affected.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner, which allows you to analyze your project without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall putri-wajit29-ruro

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback