Malicious Code Detected in bankocr Package - Security Alert

bankocr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15453: Malicious code in bankocr (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 bankocr package is an npm library designed for optical character recognition (OCR) tasks, allowing developers to integrate banking document processing capabilities into their applications. However, it has been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the bankocr package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall bankocr

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, users can remove the bankocr package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall bankocr'. Alternatively, consider using a different OCR library that does not have known vulnerabilities.

Conclusion

The bankocr package has been identified to contain malicious code, posing significant security risks to users. It is crucial to take immediate action by updating or removing the package to protect your applications from potential threats. Regular monitoring for vulnerabilities is recommended to maintain security.

See every vulnerability recorded for bankocr →

Share this vulnerability

FAQ

The bankocr package is used for optical character recognition (OCR) tasks, specifically for processing banking documents.

The malicious code was discovered by Amazon Inspector, which identified the security risk in the package.

Using the compromised bankocr package can lead to unauthorized access to sensitive data, data breaches, and other malicious activities.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application for vulnerabilities using the Vulert playground without any signup.

If you cannot update the package immediately, consider removing it from your project or using an alternative OCR library until a secure version is available.

How To Fix

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

npm uninstall bankocr

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