Malicious Code Detected in beetroot-kangaroo-chqs Package - Security Alert

beetroot-kangaroo-chqs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15567: Malicious code in beetroot-kangaroo-chqs (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 beetroot-kangaroo-chqs package is an npm library that serves various functionalities within JavaScript applications. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the beetroot-kangaroo-chqs package. This code can execute harmful actions without the user's consent, potentially compromising the integrity and security of the application. The malicious nature of this vulnerability can lead to severe consequences, including data theft, unauthorized system access, and exploitation of application resources.

How To Fix

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

npm uninstall beetroot-kangaroo-chqs

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 measure, consider using alternative packages that provide similar functionalities without the associated risks. Always ensure to review the package's security history before integrating it into your project.

Conclusion

The detection of malicious code in the beetroot-kangaroo-chqs package poses a significant threat to application security. It is essential to take immediate action by removing the package and monitoring for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for beetroot-kangaroo-chqs →

Share this vulnerability

FAQ

It is an npm library used in JavaScript applications, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

The risks include unauthorized access, data breaches, and potential exploitation of application resources.

Currently, it is recommended to uninstall the affected package. Check for updates regularly for any patched versions.

Consider using alternative packages and ensure to monitor your application for any suspicious activities.

How To Fix

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

npm uninstall beetroot-kangaroo-chqs

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