Malicious Code Detected in balpissue Package - MAL-2025-15345

balpissue Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15345: Malicious code in balpissue (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The balpissue package is an npm library designed for specific functionalities within JavaScript applications. It allows developers to integrate various features seamlessly. However, it has been identified as containing malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the balpissue package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originated from the package's initial release and affects all versions starting from 0.

How To Fix

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

npm uninstall balpissue

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 balpissue package from your project dependencies and replace it with an alternative package that offers similar functionality without the security risks. Use the following command to uninstall: npm uninstall balpissue.

Conclusion

The balpissue package has been identified as containing malicious code, posing a significant threat to applications that utilize it. It is crucial to remove this package and monitor for updates or patches. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for balpissue →

Share this vulnerability

FAQ

balpissue is an npm package used for specific functionalities in JavaScript applications, but it has been found to contain malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground.

Immediately remove the balpissue package from your project and look for alternative packages or wait for a patched version.

As of now, there is no patched version available. It is recommended to uninstall the package until a safe version is released.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring your application remains secure.

How To Fix

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

npm uninstall balpissue

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