Malicious Code Injection in entitled_herring-appteadev Package

entitled_herring-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102132: Malicious code in entitled_herring-appteadev (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

The entitled_herring-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package is characterized by its use of scripts that automate the publishing process, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in the entitled_herring-appteadev package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The origin of this vulnerability is linked to a broader campaign that aims to exploit npm's publishing mechanisms, potentially compromising the integrity of the registry and affecting developers relying on these packages.

How To Fix

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

npm uninstall entitled_herring-appteadev

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 project's dependencies using tools like Vulert, which analyzes your package-lock.json file to detect vulnerabilities in real-time. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The entitled_herring-appteadev package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their projects.

See every vulnerability recorded for entitled_herring-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability allows malicious code to modify your package.json file, potentially compromising your project's integrity and affecting the npm registry.

You should uninstall the entitled_herring-appteadev package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Regularly update your dependencies, monitor for vulnerabilities, and replace any compromised packages with secure alternatives.

How To Fix

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

npm uninstall entitled_herring-appteadev

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