Malicious Code Injection in helpless_tiglon_dumbs Package

helpless_tiglon_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103648: Malicious code in helpless_tiglon_dumbs (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 helpless_tiglon_dumbs package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which are often used to inflate developer reputation scores for token rewards. Its functionality includes creating random package names and modifying existing package metadata.

Vulnerability Detail

The vulnerability in the helpless_tiglon_dumbs package stems from its malicious code that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this issue is linked to a broader trend of malicious packages flooding npm, specifically targeting developers involved in token reward schemes.

How To Fix

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

npm uninstall helpless_tiglon_dumbs

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 workaround, you can temporarily avoid using the helpless_tiglon_dumbs package by removing it from your dependencies. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The helpless_tiglon_dumbs package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package and monitor your dependencies for similar vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for helpless_tiglon_dumbs →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry and compromise the integrity of your project by introducing unwanted packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Immediately remove the helpless_tiglon_dumbs package from your project and check for any alternative packages that can fulfill your requirements.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

Detailed information can be found in the vulnerability report on the GitHub repository of malicious packages or by consulting security advisories related to npm.

How To Fix

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

npm uninstall helpless_tiglon_dumbs

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