Malicious Code Injection in Teadg-osss-miuyts Package: A Threat to npm Users

teadg-osss-miuyts Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166768: Malicious code in teadg-osss-miuyts (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'teadg-osss-miuyts' package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality poses a significant risk to the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the 'teadg-osss-miuyts' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting other developers and users relying on npm for package management. The origin of this malicious activity is linked to the broader tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall teadg-osss-miuyts

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 'teadg-osss-miuyts' package and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The 'teadg-osss-miuyts' package poses a significant threat to npm users due to its malicious code designed to manipulate package management processes. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.

See every vulnerability recorded for teadg-osss-miuyts →

Share this vulnerability

FAQ

It is a malicious npm package part of a campaign that aims to inflate developer reputation scores through automated publishing of derivative packages.

The malicious code can compromise your project's integrity by modifying package files and republishing variants, which can lead to dependency issues and security risks.

You should uninstall the package immediately using 'npm uninstall teadg-osss-miuyts' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall teadg-osss-miuyts

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