Malicious Code Injection in tiny_locust-silentdev: A Threat to npm Users

tiny_locust-silentdev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109707: Malicious code in tiny_locust-silentdev (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

tiny_locust-silentdev is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various npm packages. However, this package has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it.

Vulnerability Detail

The vulnerability in tiny_locust-silentdev originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for applications relying on these packages.

How To Fix

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

npm uninstall tiny_locust-silentdev

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 tiny_locust-silentdev package from your project by executing:

npm uninstall tiny_locust-silentdev

This will prevent any malicious code from executing in your application.

Conclusion

The tiny_locust-silentdev package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for tiny_locust-silentdev →

Share this vulnerability

FAQ

tiny_locust-silentdev is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, potentially compromising your application's integrity and security.

You should update the package to a patched version or uninstall it to mitigate the risk of malicious code execution.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall tiny_locust-silentdev

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