Malicious Code Injection in grim_egret-appteadev: A Threat to npm Users

grim_egret-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103381: Malicious code in grim_egret-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 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

grim_egret-appteadev is a package within the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package management system. This package is linked to the tea.xyz token reward scheme, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in grim_egret-appteadev stems from its malicious payload that modifies the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The malicious code is designed to continuously republish these variants, thereby compromising the integrity of the npm ecosystem and potentially affecting developers who rely on these packages.

How To Fix

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

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

Currently, the best workaround is to avoid using grim_egret-appteadev altogether. If you have already installed it, ensure to remove it immediately and monitor your project for any dependencies that may have been affected.

Conclusion

The grim_egret-appteadev package poses a significant risk to npm users due to its malicious code that alters package configurations and pollutes the npm registry. Immediate action is required to uninstall this package and safeguard your projects from potential threats.

See every vulnerability recorded for grim_egret-appteadev →

Share this vulnerability

FAQ

grim_egret-appteadev is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious packages.

You should uninstall grim_egret-appteadev immediately and check for any other affected packages in your project.

Currently, there is no specific patch for grim_egret-appteadev. The recommended action is to uninstall the package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities by analyzing your package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

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