Malicious Code Injection in tuti-tempe93-breki: A Threat to npm Ecosystem

tuti-tempe93-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75797: Malicious code in tuti-tempe93-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 'tuti-tempe93-breki' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts designed to manipulate package metadata and inflate developer reputation scores. The package's functionality is compromised by these scripts, which can lead to significant security risks for developers and users alike.

Vulnerability Detail

The vulnerability in 'tuti-tempe93-breki' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can result in compromised applications, as developers may unknowingly install these malicious packages, exposing their projects to security threats.

How To Fix

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

npm uninstall tuti-tempe93-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 'tuti-tempe93-breki' package from your project by executing the command: 'npm uninstall tuti-tempe93-breki'. This will prevent any malicious code from executing while you seek a secure alternative package.

Conclusion

The 'tuti-tempe93-breki' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for tuti-tempe93-breki →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and repopulates the npm registry with harmful variants.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected.

If you have installed 'tuti-tempe93-breki', it is crucial to uninstall it immediately and check for any other affected packages in your project.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall tuti-tempe93-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