Malicious Code Injection in typical_antelope-appteadev Package

typical_antelope-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109895: Malicious code in typical_antelope-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 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 typical_antelope-appteadev package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the typical_antelope-appteadev package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The malicious payload can lead to unauthorized access and manipulation of the package's dependencies, posing significant risks to developers and users alike.

How To Fix

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

npm uninstall typical_antelope-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 temporary workaround, you can remove the typical_antelope-appteadev package from your project by executing: npm uninstall typical_antelope-appteadev. This will prevent any malicious code from executing while you assess your dependencies.

Conclusion

The typical_antelope-appteadev package contains a serious vulnerability that can compromise the integrity of applications relying on it. It is essential to take immediate action by updating or removing the package to safeguard your project from potential threats.

See every vulnerability recorded for typical_antelope-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript applications.

The vulnerability can lead to unauthorized modifications of your package dependencies, potentially compromising your application's security.

You should immediately update the package to the latest version or remove it from your project to mitigate the risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

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