Malicious Code Detected in hendrix-teadev: A Threat to npm Users

hendrix-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103705: Malicious code in hendrix-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'hendrix-teadev' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This functionality, while intended for legitimate use, has been exploited to inflate developer reputation scores through malicious practices.

Vulnerability Detail

The vulnerability in 'hendrix-teadev' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use malicious packages, risking their projects and reputations.

How To Fix

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

npm uninstall hendrix-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 measure, you can avoid using the 'hendrix-teadev' package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. 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 'hendrix-teadev' package poses a significant risk due to its malicious code designed to manipulate npm registry practices. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for hendrix-teadev →

Share this vulnerability

FAQ

'hendrix-teadev' is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.

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

You should uninstall the package immediately using 'npm uninstall hendrix-teadev' and review your project for any dependencies that may be affected.

Regularly update your packages, monitor your dependencies for vulnerabilities using tools like Vulert, and avoid using packages from untrusted sources.

Vulert is a tool that monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without requiring access to the code or installation.

How To Fix

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

npm uninstall hendrix-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