Critical Malicious Code Vulnerability in bgnukes Package

bgnukes Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15651: Malicious code in bgnukes (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bgnukes package is an npm module designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its integrity has been compromised due to the presence of malicious code. This vulnerability poses significant risks to applications relying on this package, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The bgnukes package has been identified to contain malicious code that can execute harmful operations within an application. This vulnerability originated from the package's codebase, which was intentionally altered to include harmful scripts. The ramifications of this vulnerability include potential data theft, unauthorized access to system resources, and the ability to execute arbitrary code, which could severely compromise application security.

How To Fix

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

npm uninstall bgnukes

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, you can remove the bgnukes package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall bgnukes'. This will help mitigate the risk while you seek alternative solutions.

Conclusion

The bgnukes package has been compromised with malicious code, posing significant risks to applications that utilize it. It is essential to update or remove the package to protect your application from potential threats. Regular monitoring of dependencies is crucial to maintain security.

See every vulnerability recorded for bgnukes →

Share this vulnerability

FAQ

The bgnukes package is an npm module used for various functionalities in JavaScript applications, but its specific use cases can vary.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

If immediate updates are not possible, consider removing the package from your project as a temporary workaround to mitigate risks.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation, including data breaches and unauthorized access.

Utilize tools like Vulert, which can monitor your package-lock.json file for vulnerabilities and provide real-time alerts.

How To Fix

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

npm uninstall bgnukes

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