Malicious Code Injection in teaadgg-osfsps-miuyts Package - npm Vulnerability

teaadgg-osfsps-miuyts Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166757: Malicious code in teaadgg-osfsps-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 teaadgg-osfsps-miuyts package is part of the tea.xyz token reward campaign that has recently flooded the npm ecosystem. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality is compromised due to its malicious intent, leading to potential security risks for users and developers alike.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the teaadgg-osfsps-miuyts package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they rely on.

How To Fix

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

npm uninstall teaadgg-osfsps-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 monitor your package dependencies using tools like Vulert. Vulert allows you to check for vulnerabilities in your package-lock.json file without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The teaadgg-osfsps-miuyts package contains malicious code that poses a significant threat to the npm ecosystem. It is essential for developers to be vigilant and remove this package from their projects to maintain security and integrity. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for teaadgg-osfsps-miuyts →

Share this vulnerability

FAQ

The teaadgg-osfsps-miuyts package is part of a campaign that generates and publishes derivative npm packages to inflate developer reputation scores for token rewards.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to npm registry pollution and security risks.

You should uninstall the teaadgg-osfsps-miuyts package immediately using the command: npm uninstall teaadgg-osfsps-miuyts.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access your code. Visit Vulert Scanner for more information.

Currently, there are no patches available for the teaadgg-osfsps-miuyts package, so the best course of action is to uninstall it.

How To Fix

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

npm uninstall teaadgg-osfsps-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