Malicious Code Detected in brinkbit-schema-permissions Package

brinkbit-schema-permissions Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16175: Malicious code in brinkbit-schema-permissions (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 brinkbit-schema-permissions package is an npm library designed to manage schema permissions within applications. It is commonly used in projects that require fine-grained control over data access and manipulation. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the brinkbit-schema-permissions package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue originates from version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall brinkbit-schema-permissions

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 workaround, you can replace the functionality provided by the brinkbit-schema-permissions package with alternative libraries that offer similar features without the associated risks. Ensure to review the security of any new packages before integrating them into your project.

Conclusion

The brinkbit-schema-permissions package has been identified as containing malicious code that poses a security threat to applications. Users are advised to uninstall the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your software without requiring access to the code.

See every vulnerability recorded for brinkbit-schema-permissions →

Share this vulnerability

FAQ

It is an npm library used for managing schema permissions in applications.

The malicious code can lead to unauthorized access and potential data breaches.

You can use the Vulert platform to monitor and alert for vulnerabilities in your application by analyzing the package-lock.json file.

The best course of action is to uninstall the brinkbit-schema-permissions package until a safe version is released.

Consider using alternative libraries that provide similar functionality without the security risks.

How To Fix

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

npm uninstall brinkbit-schema-permissions

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