Critical Malicious Code Vulnerability in bplascom Package

bplascom Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16056: Malicious code in bplascom (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 bplascom package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and various features that enhance application performance. However, this package has been identified to contain malicious code, posing a significant security risk to any application that incorporates it.

Vulnerability Detail

The vulnerability in the bplascom package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall bplascom

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 workaround, consider replacing the bplascom package with an alternative library that offers similar functionality without the associated security risks. Ensure to review the alternatives thoroughly before implementation.

Conclusion

The bplascom package has been identified to contain malicious code, posing a serious threat to applications that utilize it. Immediate action is required to mitigate this risk by removing the package or updating to a patched version if available. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for bplascom →

Share this vulnerability

FAQ

The bplascom package is an npm library used in JavaScript applications for various functionalities, enhancing performance and integration.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.

If immediate updates are not possible, consider using a workaround by replacing the bplascom package with a secure alternative until you can implement a fix.

Yes, Vulert allows you to monitor vulnerabilities using just your package-lock.json file, providing alerts without requiring code access or installation.

Detailed information about the vulnerability can be found in the official GitHub repository and through security advisories related to the bplascom package.

How To Fix

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

npm uninstall bplascom

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