Malicious Code Injection in normal_kangaroo_requirement Package

normal_kangaroo_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95661: Malicious code in normal_kangaroo_requirement (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The normal_kangaroo_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the installation and management of packages, but it has been compromised as part of a larger malicious campaign targeting npm. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of malicious packages designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the normal_kangaroo_requirement package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The origin of this vulnerability is linked to a campaign that aims to exploit the npm ecosystem by flooding it with derivative packages, thereby polluting the registry and potentially compromising other projects that depend on these packages.

How To Fix

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

npm uninstall normal_kangaroo_requirement

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 remove the normal_kangaroo_requirement package from your project by executing the command: npm uninstall normal_kangaroo_requirement. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The normal_kangaroo_requirement package has been identified as containing malicious code that can compromise your application. It is crucial to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help you monitor for such vulnerabilities in real-time.

See every vulnerability recorded for normal_kangaroo_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json file and can lead to the automatic generation of harmful packages that pollute the npm registry.

You should uninstall the package immediately and check for any updates or patches that may be released.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall normal_kangaroo_requirement

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