Malicious Code Vulnerability in xaver-sate8-miaww Package

xaver-sate8-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92412: Malicious code in xaver-sate8-miaww (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 xaver-sate8-miaww package is part of the npm ecosystem and has been identified as a component of 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, its functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the xaver-sate8-miaww package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the pollution of the npm registry. The ramifications include potential misuse of developer reputation systems and the proliferation of untrustworthy packages in the ecosystem.

How To Fix

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

npm uninstall xaver-sate8-miaww

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-sate8-miaww package and monitor your project for any dependencies that may indirectly rely on it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The xaver-sate8-miaww package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor for any related vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for xaver-sate8-miaww →

Share this vulnerability

FAQ

The xaver-sate8-miaww package is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

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

You should remove the xaver-sate8-miaww package from your project and monitor for any dependencies that may rely on it.

You can use Vulert, which monitors your package-lock.json 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 signing up.

How To Fix

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

npm uninstall xaver-sate8-miaww

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