Malicious Code Detected in boopathi Package - Security Alert

boopathi Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15966: Malicious code in boopathi (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 boopathi package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate certain tasks, but recent findings have revealed that it contains malicious code, posing a significant security risk to users and their applications. The package's popularity may lead to widespread adoption, increasing the potential impact of this vulnerability.

Vulnerability Detail

The vulnerability in the boopathi package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, execute harmful operations, or facilitate further attacks on the system. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall boopathi

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 an immediate workaround, consider replacing the boopathi package with an alternative library that provides similar functionality without the associated risks. Ensure to review the alternatives for security and reliability before implementation.

Conclusion

The discovery of malicious code in the boopathi package poses a serious threat to users and their applications. Immediate action is required to uninstall the package and seek alternatives. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure the security of your software.

See every vulnerability recorded for boopathi →

Share this vulnerability

FAQ

The boopathi package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

The malicious code can compromise your application's security, potentially leading to unauthorized access to sensitive data and other harmful actions.

You should uninstall the boopathi package immediately and consider using an alternative library until a secure version is 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 if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall boopathi

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