Malicious Code Injection in silent_tiglon_0xrequest: npm Package Vulnerability

silent_tiglon_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108675: Malicious code in silent_tiglon_0xrequest (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 package silent_tiglon_0xrequest is part of a broader campaign associated with the tea.xyz token reward initiative. It is designed to facilitate automatic publishing of derivative packages to inflate developer reputation scores. This package, like others in the campaign, is vulnerable to malicious code injections that compromise its integrity and the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the package's involvement in a malicious campaign that modifies its package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can mislead developers into using compromised packages. The origin of this vulnerability is linked to the autopublish scripts that are included in the package, which are designed to automate the creation and publication of these malicious derivatives.

How To Fix

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

npm uninstall silent_tiglon_0xrequest

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, you can remove the silent_tiglon_0xrequest package from your project to prevent any potential exploitation. Use the following command to uninstall the package: npm uninstall silent_tiglon_0xrequest.

Conclusion

The silent_tiglon_0xrequest package poses a significant security risk due to its involvement in a malicious campaign that alters its functionality. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats.

See every vulnerability recorded for silent_tiglon_0xrequest →

Share this vulnerability

FAQ

silent_tiglon_0xrequest is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

If you have installed silent_tiglon_0xrequest, it is recommended to uninstall it immediately and check for any other affected packages.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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

How To Fix

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

npm uninstall silent_tiglon_0xrequest

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