Critical Malicious Code Vulnerability in bjt4 Package

bjt4 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15772: Malicious code in bjt4 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The bjt4 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its recent discovery of malicious code poses significant risks to users. This vulnerability can compromise application integrity and user data, making it crucial for developers to address it promptly.

Vulnerability Detail

The bjt4 package has been identified to contain malicious code that can lead to unauthorized access and potential data breaches. This vulnerability originated from the package's codebase, which was compromised, allowing attackers to exploit it. The ramifications of this vulnerability include the risk of data theft, application malfunction, and potential exploitation of user systems.

How To Fix

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

npm uninstall bjt4

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 measure, consider removing the bjt4 package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall bjt4'. This will help mitigate the risk of exploitation while waiting for a fix.

Conclusion

The discovery of malicious code in the bjt4 package poses a serious threat to users and their applications. It is essential to take immediate action by updating or removing the package to safeguard against potential exploitation. Staying informed and utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for bjt4 →

Share this vulnerability

FAQ

The bjt4 package is an npm library used for various functionalities in JavaScript applications, but its specific use cases may vary based on the project.

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 you cannot update the package right away, consider removing it from your project as a temporary workaround to minimize risk.

Detailed information about this vulnerability can be found on the GitHub repository of the malicious packages project.

Vulert uses your package-lock.json file to monitor and alert you in real-time for any open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall bjt4

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