Malicious Code Injection in putri-getas63-breki: A Threat to npm Ecosystem

putri-getas63-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74980: Malicious code in putri-getas63-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'putri-getas63-breki' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's publishing system by generating numerous derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is primarily centered around autopublishing scripts that automate the creation and publication of these malicious packages.

Vulnerability Detail

The vulnerability in 'putri-getas63-breki' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The ramifications include potential security risks for developers who unknowingly use these packages, as well as a degradation of the npm registry's reliability.

How To Fix

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

npm uninstall putri-getas63-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-getas63-breki' package and any other packages that appear suspicious. Implementing a package monitoring tool like Vulert can help you identify and alert you to vulnerabilities in your dependencies. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The 'putri-getas63-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for putri-getas63-breki →

Share this vulnerability

FAQ

'putri-getas63-breki' is an npm package that is part of a malicious campaign aimed at manipulating the npm ecosystem for token rewards.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and the integrity of your application.

You should uninstall the package immediately using 'npm uninstall putri-getas63-breki' and review your project's dependencies for any other suspicious packages.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

You can find detailed information about this vulnerability in the vulnerability report provided by Amazon Inspector and other security resources.

How To Fix

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

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