Malicious Code Injection in putri-teh32-ruro: A Threat to npm Packages

putri-teh32-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107550: Malicious code in putri-teh32-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 package 'putri-teh32-ruro' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of derivative packages, which are automatically generated and published to inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to the integrity of the npm registry and the developers using it.

Vulnerability Detail

The vulnerability in 'putri-teh32-ruro' originates from its association with a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages.

How To Fix

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

npm uninstall putri-teh32-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-teh32-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The 'putri-teh32-ruro' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for putri-teh32-ruro →

Share this vulnerability

FAQ

The vulnerability can lead to the pollution of the npm registry, making it difficult for developers to find reliable packages and potentially compromising the security of their applications.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed the package, you should uninstall it immediately using the command 'npm uninstall putri-teh32-ruro' and review your other dependencies for potential vulnerabilities.

Yes, consider looking for other npm packages that offer similar functionality but do not have the same malicious behavior.

Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review the source of packages before installation.

How To Fix

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

npm uninstall putri-teh32-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