Malicious Code Injection in very_tiglon_0xrequest Package

very_tiglon_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110449: Malicious code in very_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The very_tiglon_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish variants that can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the very_tiglon_0xrequest package stems from its malicious code, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior can lead to security risks, including unauthorized access to sensitive information and potential exploitation of affected applications.

How To Fix

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

npm uninstall very_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 workaround, you can prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package in its dependencies or devDependencies.

Conclusion

The very_tiglon_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for very_tiglon_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The malicious code can lead to unauthorized changes in your application's dependencies, potentially exposing it to security risks.

You should uninstall the very_tiglon_0xrequest package immediately and check for any affected dependencies.

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

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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