Malicious Code Injection in putri-mendut8-breki Package

putri-mendut8-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75020: Malicious code in putri-mendut8-breki (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The putri-mendut8-breki 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. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the putri-mendut8-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This behavior not only compromises the integrity of the npm registry but also inflates developer reputation scores fraudulently. The malicious payload can lead to significant pollution of the npm ecosystem, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall putri-mendut8-breki

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-mendut8-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The putri-mendut8-breki package has been identified as a malicious package that compromises the integrity of the npm ecosystem. It is crucial to uninstall this package and monitor your project for any vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential risks in your dependencies.

See every vulnerability recorded for putri-mendut8-breki →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, removes private flags, and floods the npm registry with unwanted package variants, which can lead to confusion and potential security risks.

You should uninstall the putri-mendut8-breki package immediately using the command npm uninstall putri-mendut8-breki and check for any dependencies that may be affected.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that offer similar functionality without the associated risks of malicious code.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall putri-mendut8-breki

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