Malicious Code Vulnerability in bcp-security-update Package

bcp-security-update Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1658: Malicious code in bcp-security-update (npm). Affects bcp-security-update versions 1.0.7. 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 bcp-security-update package is an npm module designed to enhance security updates for applications. It aims to streamline the process of applying security patches and updates to dependencies. However, this package has been identified as containing malicious code, which poses a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the bcp-security-update package, specifically in version 1.0.7. This code can lead to unauthorized access, data breaches, or the execution of harmful actions within the affected application. The malicious nature of this code was identified by ReversingLabs, which reported the issue, highlighting the importance of vigilance when using third-party packages.

How To Fix

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

npm uninstall bcp-security-update

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 avoid using the bcp-security-update package altogether and manually apply security updates to your dependencies. This can be done by regularly checking for updates and applying them as necessary.

Conclusion

The bcp-security-update package has been found to contain malicious code, posing a significant threat to applications that utilize it. It is essential to take immediate action by removing the affected version and monitoring for updates. Utilizing tools like Vulert can aid in identifying vulnerabilities in your software.

See every vulnerability recorded for bcp-security-update →

Share this vulnerability

FAQ

The bcp-security-update package is an npm module that helps manage and apply security updates for software dependencies.

The malicious code was identified by ReversingLabs, which specializes in analyzing and reporting on security vulnerabilities in software packages.

The risks include unauthorized access to sensitive data, potential data breaches, and the execution of harmful actions within the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.

If immediate updates are not possible, consider implementing a workaround by manually managing security updates for your dependencies and avoiding the use of the bcp-security-update package.

How To Fix

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

npm uninstall bcp-security-update

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