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

putri-kue80-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107498: Malicious code in putri-kue80-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-kue80-ruro' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter package metadata, which can lead to significant issues in the npm ecosystem.

Vulnerability Detail

The vulnerability in 'putri-kue80-ruro' originates from its association with a malicious campaign that employs scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.

How To Fix

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

npm uninstall putri-kue80-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-kue80-ruro' package and monitor your project for any dependencies that may indirectly include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The 'putri-kue80-ruro' package poses a significant threat due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for putri-kue80-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed 'putri-kue80-ruro', it is recommended to remove it immediately and monitor your project for any related vulnerabilities.

Yes, tools like Vulert can help monitor your package-lock.json for open-source vulnerabilities in real-time.

Using compromised packages can lead to security vulnerabilities, data breaches, and a compromised development environment.

How To Fix

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

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