Malicious Code Detected in bgrt4s Package - Security Alert

bgrt4s Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15652: Malicious code in bgrt4s (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 bgrt4s package is an npm library that serves specific functionalities within JavaScript applications. It is designed to enhance user experience by providing various utilities. However, it has been identified as containing malicious code, which poses significant security risks to applications that utilize this package.

Vulnerability Detail

The vulnerability in the bgrt4s package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate 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 bgrt4s

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

If an immediate update is not feasible, consider removing the bgrt4s package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall bgrt4s'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The bgrt4s package has been identified as containing malicious code, posing significant risks to applications that utilize it. Immediate action is required to either update or remove the package to safeguard your application from potential threats.

See every vulnerability recorded for bgrt4s →

Share this vulnerability

FAQ

The bgrt4s package is an npm library used in JavaScript applications for various utility functions.

The malicious code can lead to unauthorized access, data breaches, or execution of harmful commands within affected applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

As of now, there is no patched version available. Users are advised to monitor the official repository for updates.

If an update is not possible, it is recommended to uninstall the bgrt4s package to mitigate risks until a secure version is released.

How To Fix

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

npm uninstall bgrt4s

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