Malicious Code Injection in aesthetic_moth-appteadev Package

aesthetic_moth-appteadev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99229: Malicious code in aesthetic_moth-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 aesthetic_moth-appteadev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package, like others in the campaign, contains scripts designed to automatically publish derivative packages with altered names and metadata, leading to potential security risks.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the aesthetic_moth-appteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The origin of this issue is linked to a broader campaign that exploits npm's publishing capabilities to manipulate developer reputation and reward systems.

How To Fix

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

npm uninstall aesthetic_moth-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 aesthetic_moth-appteadev package from your project to mitigate the risks associated with this vulnerability. Use the following command: npm uninstall aesthetic_moth-appteadev.

Conclusion

The aesthetic_moth-appteadev package contains malicious code that poses significant risks to projects utilizing it. It is crucial to take immediate action by updating or uninstalling the package to safeguard your application. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for aesthetic_moth-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The malicious code modifies your package.json file and can lead to the publication of unauthorized packages, compromising your project's integrity.

You should update the package to a patched version or uninstall it to avoid potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check if your application is affected.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to minimize risks.

How To Fix

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

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