Malicious Code Injection in jaja-rangi31-tititugel: npm Package Vulnerability

jaja-rangi31-tititugel Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97963: Malicious code in jaja-rangi31-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 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 jaja-rangi31-tititugel package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. Its primary functionality is to serve as a component in the token reward system, but it has been compromised to include malicious scripts that affect its integrity and the npm registry.

Vulnerability Detail

The vulnerability in jaja-rangi31-tititugel stems from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. This behavior is designed to inflate developer reputation scores for token rewards, ultimately polluting the npm registry and potentially compromising other packages.

How To Fix

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

npm uninstall jaja-rangi31-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, you can prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package by auditing your dependencies regularly.

Conclusion

The jaja-rangi31-tititugel package has been identified as containing malicious code that compromises the npm registry and developer reputation systems. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for jaja-rangi31-tititugel →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign but has been compromised to include malicious code.

The vulnerability can lead to the automatic publication of malicious packages, potentially compromising your project's integrity and security.

You should uninstall the package immediately and monitor your dependencies for any other malicious packages.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall jaja-rangi31-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