Malicious Code Detected in buffer-8or Package - Immediate Action Required

buffer-8or Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16284: Malicious code in buffer-8or (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 buffer-8or package is an npm module designed for handling buffer operations in JavaScript applications. It is commonly used for data manipulation and processing tasks. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the buffer-8or package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and has been flagged as a serious threat by security researchers.

How To Fix

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

npm uninstall buffer-8or

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 temporarily disable the functionality that relies on the buffer-8or package until a secure alternative is implemented. This can be done by commenting out the relevant code sections in your application that utilize this package.

Conclusion

The buffer-8or package has been identified as containing malicious code, posing a significant risk to applications that utilize it. Immediate action is required to remove the package and safeguard your application from potential threats. Utilize tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for buffer-8or →

Share this vulnerability

FAQ

The buffer-8or package is an npm module used for buffer operations in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using this package.

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 advised to uninstall the package until a secure alternative is found.

You should immediately remove the buffer-8or package from your project and replace it with a secure alternative.

Related vulnerabilities

Recent vulnerabilities recorded for buffer-8or.

How To Fix

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

npm uninstall buffer-8or

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