Malicious Code Injection in tomi-getas95-breki: A Threat to npm Users

tomi-getas95-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75691: Malicious code in tomi-getas95-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 package tomi-getas95-breki is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. It aims to inflate developer reputation scores for token rewards, making it a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in tomi-getas95-breki stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk of reputation damage to developers and can lead to the inadvertent use of compromised packages in applications.

How To Fix

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

npm uninstall tomi-getas95-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 tomi-getas95-breki package and replace it with a trusted alternative. Ensure that your package.json does not include this malicious package and monitor your dependencies for any unauthorized changes.

Conclusion

The tomi-getas95-breki package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for tomi-getas95-breki →

Share this vulnerability

FAQ

tomi-getas95-breki is an npm package that has been identified as malicious, designed to manipulate the npm registry for token reward purposes.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should immediately uninstall the tomi-getas95-breki package and review your project's dependencies for any other malicious packages.

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

There is no patch for the tomi-getas95-breki package as it is inherently malicious. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall tomi-getas95-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