Malicious Code Injection in hayes-teadev Package

hayes-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103616: Malicious code in hayes-teadev (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The hayes-teadev package is part of the npm ecosystem, primarily used for development purposes. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the hayes-teadev package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall hayes-teadev

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 hayes-teadev package until a secure version is released. Additionally, you can manually inspect your package.json file to ensure that no unauthorized changes have been made.

Conclusion

The hayes-teadev package is compromised by a malicious campaign that alters its functionality and can affect developers using it. It is essential to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help in monitoring and identifying such vulnerabilities in real-time.

See every vulnerability recorded for hayes-teadev →

Share this vulnerability

FAQ

The hayes-teadev package is an npm package associated with the tea.xyz token reward campaign, which is known for manipulating developer reputation scores.

This vulnerability can lead to unauthorized changes in your project's package.json file, potentially compromising your project's integrity and security.

If you have installed the hayes-teadev package, it is crucial to update it to the latest version or remove it from your project until a secure version is available.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall hayes-teadev

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