Malicious Code Injection in timnwd-devapptea Package - npm Vulnerability

timnwd-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109701: Malicious code in timnwd-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 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 timnwd-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on the npm registry. This package is designed to facilitate the generation and publication of derivative packages that aim to inflate developer reputation scores for token rewards. Its functionality includes automatic publishing scripts that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the timnwd-devapptea package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry and potentially compromising other packages and applications that depend on it. The origin of this issue is linked to the broader tea.xyz token reward initiative, which has exploited npm's publishing capabilities.

How To Fix

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

npm uninstall timnwd-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 workaround, you can temporarily avoid using the timnwd-devapptea package by removing it from your package.json and running npm install to refresh your dependencies. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The timnwd-devapptea package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for timnwd-devapptea →

Share this vulnerability

FAQ

The timnwd-devapptea package is part of a malicious campaign that generates and publishes derivative npm packages to inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry, potentially compromising other packages and applications that depend on the affected package.

You should remove the timnwd-devapptea package from your project and monitor for any updates or patches that may be released.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, 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 timnwd-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