Malicious Code Injection in putri-mangut24-breki Package

putri-mangut24-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75015: Malicious code in putri-mangut24-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The putri-mangut24-breki package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the putri-mangut24-breki package arises from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The malicious payload is part of a broader strategy to exploit npm for token rewards, posing risks such as reputation damage for developers and the potential for malicious packages to proliferate within the ecosystem.

How To Fix

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

npm uninstall putri-mangut24-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 remove the putri-mangut24-breki package from your project by executing the following command: npm uninstall putri-mangut24-breki. This will prevent any malicious code from executing while you seek a permanent fix.

Conclusion

The putri-mangut24-breki package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for putri-mangut24-breki →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at manipulating the npm registry for token rewards.

The malicious code modifies your package.json file, potentially leading to the publication of unwanted packages and compromising your project's integrity.

You should uninstall the package immediately and check for any unauthorized changes to your package.json file.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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