Malicious Code Injection in burch-teadev Package: A Threat to npm Ecosystem

burch-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100191: Malicious code in burch-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 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 burch-teadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of such packages is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. However, this functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the burch-teadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and creating random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising other packages and applications that depend on it. The ramifications include loss of control over package integrity, potential data breaches, and a general degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall burch-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 remove the burch-teadev package from your project by executing the command: npm uninstall burch-teadev. This will prevent any malicious code from executing while you assess the situation and look for a secure alternative package.

Conclusion

The burch-teadev package poses a significant security risk due to the embedded malicious code that alters package configurations and floods the npm registry with derivative packages. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for burch-teadev →

Share this vulnerability

FAQ

The burch-teadev package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The malicious code modifies your package.json file, potentially compromising your application's integrity and security by removing private flags and altering version numbers.

If you have installed burch-teadev, it is recommended to uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.

To prevent future vulnerabilities, regularly update your packages, use tools like Vulert for monitoring, and review package dependencies for any suspicious activity.

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 burch-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