Critical Malicious Code Vulnerability in bsgiowrmnkhjzktx Package

bsgiowrmnkhjzktx Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16230: Malicious code in bsgiowrmnkhjzktx (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 bsgiowrmnkhjzktx package is an npm module designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its security has come into question due to the discovery of malicious code embedded within it. This vulnerability poses a significant risk to applications that rely on this package, potentially leading to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the bsgiowrmnkhjzktx package originates from the inclusion of malicious code that can execute harmful actions within the user's environment. This could lead to data theft, unauthorized access to sensitive information, or even complete system compromise. The malicious nature of the code makes it imperative for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall bsgiowrmnkhjzktx

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 bsgiowrmnkhjzktx package in your application until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the bsgiowrmnkhjzktx package highlights the importance of maintaining vigilance in open-source software usage. Users are urged to take immediate action to remove the affected package and monitor their applications for any potential security threats.

See every vulnerability recorded for bsgiowrmnkhjzktx →

Share this vulnerability

FAQ

The bsgiowrmnkhjzktx package is an npm module used in JavaScript applications for various functionalities.

The malicious code was identified through security audits and reports from security researchers, including Amazon Inspector.

The risks include unauthorized access to sensitive data, potential data breaches, and system compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If immediate removal is not possible, consider isolating the affected application and monitoring it closely for any suspicious activity.

How To Fix

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

npm uninstall bsgiowrmnkhjzktx

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