Malicious Code Detected in brsnyder Package - Security Alert

brsnyder Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16211: Malicious code in brsnyder (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 brsnyder package is an npm library that provides various functionalities for developers. However, it has been identified to contain malicious code that poses a significant security risk to applications utilizing this package. Users of brsnyder should be aware of its potential vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the brsnyder package originates from the inclusion of malicious code that can compromise the security of applications using it. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability is present in all versions starting from 0, making it critical for users to address it immediately.

How To Fix

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

npm uninstall brsnyder

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, consider replacing the brsnyder package with an alternative library that provides similar functionality without the security risks. Review your project's dependencies and ensure that no other vulnerable packages are present.

Conclusion

The discovery of malicious code in the brsnyder package poses a serious threat to applications using it. Users are urged to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for brsnyder →

Share this vulnerability

FAQ

brsnyder is an npm package that offers various functionalities for developers, but it has been found to contain malicious code.

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

If you are using brsnyder, it is recommended to remove the package immediately and look for alternatives or wait for a patched version.

Currently, there is no patch available for the brsnyder package. Users should remove the package until a secure version is released.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, providing an easy way to keep your applications secure.

How To Fix

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

npm uninstall brsnyder

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