Malicious Code Injection in putri-lumpur29-breki Package

putri-lumpur29-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75010: Malicious code in putri-lumpur29-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 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-lumpur29-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as malicious due to its capability to modify package metadata and republish variants that can pollute the npm registry.

Vulnerability Detail

The vulnerability in the putri-lumpur29-breki package originates from its inclusion in a malicious campaign that employs autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers by altering package.json files, removing private flags, and changing version numbers. The continuous republishing of these variants can lead to confusion and potential security risks for users relying on legitimate packages.

How To Fix

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

npm uninstall putri-lumpur29-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 measure, you can avoid using the putri-lumpur29-breki package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies to identify and remove any malicious packages.

Conclusion

The putri-lumpur29-breki package has been identified as a malicious entity within the npm ecosystem, capable of compromising project integrity through unauthorized modifications. It is crucial to remove this package and monitor for updates to ensure the security of your projects.

See every vulnerability recorded for putri-lumpur29-breki →

Share this vulnerability

FAQ

The putri-lumpur29-breki package is an npm package associated with a token reward campaign that has been identified as malicious.

This vulnerability can lead to the modification of your project's package.json file, potentially compromising your project's integrity and security.

You should remove the putri-lumpur29-breki package from your project and monitor for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about the packages you use.

How To Fix

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

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