Malicious Code Injection in hadi-rendang61-tititugel Package

hadi-rendang61-tititugel Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97870: Malicious code in hadi-rendang61-tititugel (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The hadi-rendang61-tititugel package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to enhance developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers by inflating reputation scores fraudulently. The scripts involved typically include auto.js, autopublish.js, autopublish2.js, and autopublish3.js.

How To Fix

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

npm uninstall hadi-rendang61-tititugel

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, consider using a different package that provides similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time based on your package-lock.json file.

Conclusion

The hadi-rendang61-tititugel package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and affect developers' reputation scores. It is crucial to remove this package and monitor your dependencies for vulnerabilities.

See every vulnerability recorded for hadi-rendang61-tititugel →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

The package modifies the package.json file, removes private flags, changes version numbers, and continuously republishes variants to pollute the npm registry.

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

You should uninstall the package immediately using the command: npm uninstall hadi-rendang61-tititugel.

Yes, Vulert provides a service that monitors your package-lock.json for vulnerabilities and alerts you in real-time.

How To Fix

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

npm uninstall hadi-rendang61-tititugel

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