Malicious Code Injection in jacobs-tea-archive: A Threat to npm Users

jacobs-tea-archive Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104493: Malicious code in jacobs-tea-archive (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

jacobs-tea-archive is an npm package that appears to be part of a broader campaign related to the tea.xyz token reward system. This package is designed to facilitate the distribution of derivative packages, which can inflate developer reputation scores. The package's functionality is compromised due to the presence of malicious scripts that alter its metadata and behavior, posing a significant risk to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in jacobs-tea-archive stems from its association with a malicious campaign that utilizes scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can result in developers inadvertently using compromised packages, which may lead to security breaches or data loss.

How To Fix

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

npm uninstall jacobs-tea-archive

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, users can remove the jacobs-tea-archive package from their project until a secure version is released. This can be done using the command: 'npm uninstall jacobs-tea-archive'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The jacobs-tea-archive package poses a significant threat due to its malicious code that alters package metadata and behavior. Users are advised to uninstall the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for jacobs-tea-archive →

Share this vulnerability

FAQ

jacobs-tea-archive is an npm package involved in a token reward campaign that has been identified as malicious.

The vulnerability can lead to the introduction of compromised packages into your project, potentially resulting in security breaches.

You should uninstall the package immediately and monitor your project for any unusual behavior.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.

How To Fix

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

npm uninstall jacobs-tea-archive

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