Malicious Code Injection in xaver-bubur82-tititugel: A Threat to npm Users

xaver-bubur82-tititugel Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98518: Malicious code in xaver-bubur82-tititugel (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 package xaver-bubur82-tititugel is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that modify package metadata, leading to potential security risks.

Vulnerability Detail

The vulnerability in xaver-bubur82-tititugel stems from its inclusion in a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious code, which can lead to further exploitation of applications relying on these packages.

How To Fix

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

npm uninstall xaver-bubur82-tititugel

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 xaver-bubur82-tititugel package and replace it with a trusted alternative. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The xaver-bubur82-tititugel package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant about their dependencies and to take immediate action to remove any affected packages. Regular audits and the use of monitoring tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for xaver-bubur82-tititugel →

Share this vulnerability

FAQ

xaver-bubur82-tititugel is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

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

If you have installed xaver-bubur82-tititugel, you should uninstall it immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities by analyzing your package-lock.json file.

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

How To Fix

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

npm uninstall xaver-bubur82-tititugel

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