Malicious Code Injection in allied_tarsier-silentdev: A Threat to npm Packages

allied_tarsier-silentdev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99360: Malicious code in allied_tarsier-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package allied_tarsier-silentdev is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability in allied_tarsier-silentdev stems from its inclusion in a malicious campaign that deploys scripts designed to automatically publish derivative packages with altered metadata. These scripts, such as auto.js and autopublish.js, modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall allied_tarsier-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 allied_tarsier-silentdev package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall allied_tarsier-silentdev'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The allied_tarsier-silentdev package poses a significant security risk due to its malicious code injection. It is crucial for developers to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to safeguard their applications against potential vulnerabilities.

See every vulnerability recorded for allied_tarsier-silentdev →

Share this vulnerability

FAQ

It is an npm package that has been associated with a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert to monitor your application for vulnerabilities without needing to access the code or installation.

Regularly update your packages, use trusted sources, and employ tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

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