Malicious Code Injection in initial_locust-appteadev Package

initial_locust-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104200: Malicious code in initial_locust-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The initial_locust-appteadev package is part of the npm ecosystem, primarily used for developing applications with Node.js. It is designed to facilitate various functionalities within the application development process. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, affecting developers and their projects.

Vulnerability Detail

The vulnerability in the initial_locust-appteadev package stems from its association with the tea.xyz token reward campaign. This package contains malicious scripts that automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall initial_locust-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 measure, avoid using the initial_locust-appteadev package and consider using alternative packages that provide similar functionality without the associated risks. Always validate the integrity of packages before including them in your project.

Conclusion

The initial_locust-appteadev package poses a significant security risk due to its malicious code that alters package configurations and pollutes the npm registry. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for initial_locust-appteadev →

Share this vulnerability

FAQ

It is an npm package used in Node.js application development, but it has been compromised with malicious code.

The malicious code modifies your package.json file and repopulates the npm registry with harmful variants, potentially compromising your application's security.

You should uninstall the initial_locust-appteadev package immediately and replace it with a secure alternative.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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