Malicious Code Injection in jefqob-devapptea: A Threat to npm Ecosystem

jefqob-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104543: Malicious code in jefqob-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

jefqob-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is intended for developers looking to leverage token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in jefqob-devapptea originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The ramifications include pollution of the npm registry and potential exploitation of developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall jefqob-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 monitor your package dependencies using tools like Vulert. By utilizing Vulert's playground, you can check if your application is affected by this vulnerability without any signup. Simply upload your package-lock.json file to receive real-time alerts for open-source vulnerabilities.

Conclusion

The jefqob-devapptea package poses a significant threat due to its malicious code that compromises the npm ecosystem. It is crucial for developers to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for jefqob-devapptea →

Share this vulnerability

FAQ

jefqob-devapptea is an npm package associated with the tea.xyz token reward campaign, designed to help developers earn token rewards.

The malicious code modifies your package.json, removes private flags, and publishes random packages, which can lead to reputation damage and security risks.

You should uninstall the package immediately using the command: npm uninstall jefqob-devapptea.

Yes, regularly monitor your dependencies with tools like Vulert to receive alerts for any open-source vulnerabilities.

Yes, you can use Vulert's playground to upload your package-lock.json file and check for vulnerabilities without any signup.

How To Fix

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

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