Malicious Code Injection in formidable_asp-appteadev Package

formidable_asp-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102869: Malicious code in formidable_asp-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 formidable_asp-appteadev package is part of the npm ecosystem and is used for various application development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publishing of derivative packages. This vulnerability poses a significant risk to developers and users relying on this package.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the formidable_asp-appteadev package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. This behavior not only pollutes the npm ecosystem but also compromises the integrity of applications that depend on this package. The malicious code is part of a broader scheme linked to the tea.xyz token reward campaign, which exploits npm for fraudulent gains.

How To Fix

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

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

If an immediate update is not feasible, consider removing the formidable_asp-appteadev package from your project until a secure version is released. You can do this by executing: npm uninstall formidable_asp-appteadev. Additionally, monitor your package-lock.json file for any unexpected changes.

Conclusion

The formidable_asp-appteadev package has been identified as containing malicious code that poses significant risks to developers and applications. It is crucial to update or remove this package to maintain the integrity and security of your projects. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.

See every vulnerability recorded for formidable_asp-appteadev →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package.json files and repackages the software, leading to potential security risks.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As a temporary measure, you can uninstall the package and monitor your package-lock.json file for any unauthorized changes.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

Failing to address this vulnerability could lead to compromised applications, data breaches, and damage to your reputation as a developer.

How To Fix

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

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