Critical Malicious Code Vulnerability in buffer-yor Package

buffer-yor Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16303: Malicious code in buffer-yor (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 buffer-yor package is an npm library designed for handling buffer operations in JavaScript applications. It provides developers with utilities to manipulate binary data efficiently. However, the package has been found to contain malicious code, posing significant risks to applications that rely on it, potentially leading to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the buffer-yor package stems from the inclusion of malicious code that can execute harmful operations when the package is used in an application. This code was introduced in version 0 and can compromise the security of any application utilizing this package, leading to potential data theft, unauthorized access, or other malicious activities.

How To Fix

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

npm uninstall buffer-yor

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 buffer-yor package with an alternative library that provides similar functionality without the associated risks. Always ensure to review the security of any new package before integrating it into your application.

Conclusion

The buffer-yor package has been identified as containing malicious code, posing serious security risks to applications. It is essential to uninstall the package and monitor for updates or alternatives to ensure the safety of your software.

See every vulnerability recorded for buffer-yor →

Share this vulnerability

FAQ

The buffer-yor package is an npm library used for handling buffer operations in JavaScript applications.

The malicious code can execute harmful operations, potentially leading to unauthorized access or data breaches.

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.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

Uninstall the buffer-yor package immediately and consider using an alternative library for buffer operations.

Related vulnerabilities

Recent vulnerabilities recorded for buffer-yor.

How To Fix

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

npm uninstall buffer-yor

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