Malicious Code Detected in bjtcore Package - Security Alert

bjtcore Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15773: Malicious code in bjtcore (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 bjtcore package is a Node.js library commonly used in various applications for its functionalities related to data processing and manipulation. It is designed to provide developers with a set of tools to streamline their coding efforts. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the bjtcore package stems from the inclusion of malicious code that can compromise the integrity of applications using this library. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The issue originates from 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 bjtcore

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, developers can isolate the bjtcore package in a separate environment or use a different library that offers similar functionalities without the associated risks. Additionally, consider using tools like Vulert to monitor your application for vulnerabilities.

Conclusion

The discovery of malicious code in the bjtcore package highlights the importance of maintaining secure coding practices and regularly monitoring dependencies for vulnerabilities. Users must take immediate action to mitigate risks associated with this package.

See every vulnerability recorded for bjtcore →

Share this vulnerability

FAQ

bjtcore is a Node.js library used for data processing and manipulation in various applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

You should remove the bjtcore package from your project and replace it with a secure alternative immediately.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall bjtcore

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