Malicious Code Vulnerability in maya-teadf-daffm: Exploitation of npm Package for Reputation Inflation

maya-teadf-daffm Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160251: Malicious code in maya-teadf-daffm (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'maya-teadf-daffm' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names. This functionality is exploited to inflate developer reputation scores for rewards associated with the tea protocol, making it a target for malicious activities.

Vulnerability Detail

The vulnerability originates from the malicious design of the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages and projects that rely on npm.

How To Fix

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

npm uninstall maya-teadf-daffm

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your project. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'maya-teadf-daffm' package poses a significant risk due to its malicious design aimed at inflating developer reputation scores. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the security and integrity of their applications.

See every vulnerability recorded for maya-teadf-daffm →

Share this vulnerability

FAQ

The impact includes the potential for reputation inflation in the npm registry, which can lead to the proliferation of malicious packages and compromise the integrity of other projects.

You can use tools like Vulert to scan your package-lock.json file for vulnerabilities, or manually check your dependencies for the presence of the affected package.

Currently, there is no specific patch for the 'maya-teadf-daffm' package. The best course of action is to remove the package from your project.

If you have installed the package, it is recommended to uninstall it immediately using the command: npm uninstall maya-teadf-daffm.

Yes, Vulert can monitor your project for open-source vulnerabilities in real-time, using just your package-lock.json file.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall maya-teadf-daffm

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