Malicious Code Injection in ouufsy-devapptea Package

ouufsy-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106854: Malicious code in ouufsy-devapptea (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ouufsy-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.

Vulnerability Detail

The vulnerability in the ouufsy-devapptea package originates from its design to include autopublish scripts that alter the package.json file. This modification removes private flags, changes version numbers, and generates random package names, which can lead to significant pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce unwanted code into their projects.

How To Fix

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

npm uninstall ouufsy-devapptea

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 ouufsy-devapptea package from your project by executing the following command: npm uninstall ouufsy-devapptea. This will prevent any malicious code from executing in your application until a fix is applied.

Conclusion

The ouufsy-devapptea package contains a significant vulnerability that allows for the injection of malicious code, which can compromise the security of projects using it. It is crucial to take immediate action by updating or removing the package to protect your application.

See every vulnerability recorded for ouufsy-devapptea →

Share this vulnerability

FAQ

ouufsy-devapptea is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing numerous derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You can use Vulert, which monitors open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check your application without any signup.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate the risk.

More information can be found on the official GitHub repository or through security advisories related to npm packages.

How To Fix

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

npm uninstall ouufsy-devapptea

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