Malicious Package in buffes-xor

buffes-xor Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.8

GHSA-28f4-mjfq-qrvf: Malicious Package in buffes-xor. Affects buffes-xor versions >= 0.0.0. 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 buffes-xor package is an npm package that is used in various projects for XOR encryption and decryption. It provides a simple and efficient way to perform XOR operations on buffers. The package has been widely adopted due to its ease of use and performance. However, version 2.0.2 of the package contained malicious code that targeted the Ethereum cryptocurrency. This code performed unauthorized transactions to wallets not controlled by the user, potentially resulting in the loss of Ethereum funds.

Vulnerability Detail

The vulnerability in version 2.0.2 of the buffes-xor package allowed an attacker to execute unauthorized transactions targeting Ethereum wallets. This was achieved through the inclusion of malicious code in the package. The code was designed to bypass user authentication and perform transactions to external wallets without the user's knowledge or consent. The impact of this vulnerability could be significant, as it could result in the loss of Ethereum funds for affected users.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The buffes-xor package version 2.0.2 contained malicious code that targeted Ethereum wallets, allowing unauthorized transactions to be performed. To mitigate this vulnerability, it is crucial to remove the package from your environment and ensure that no Ethereum funds were compromised. Stay vigilant and report any suspicious activity to the appropriate authorities. For further assistance with vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for buffes-xor →

Share this vulnerability

FAQ

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it to identify any vulnerable packages.

If you find that your project is affected by this vulnerability, you should immediately remove the buffes-xor package from your environment. Additionally, review your Ethereum wallet transactions to ensure no unauthorized transactions have occurred. If any unauthorized transactions are identified, take appropriate action to secure your funds and report the incident.

Yes, there are alternative packages available for XOR encryption and decryption. Some popular options include 'xor-crypt' and 'xor-crypto'. It is recommended to carefully review and vet any alternative packages before integrating them into your project.

Yes, the malicious code has been removed in subsequent versions of the buffes-xor package. It is important to ensure that you are using a version of the package that is free from the vulnerability. Always update to the latest version of the package to mitigate any potential security risks.

If you have identified this vulnerability or have any additional information related to it, you can report it to the package maintainer or the relevant security authorities. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

Related vulnerabilities

Recent vulnerabilities recorded for buffes-xor.

How To Fix

No fixed version is published for this vulnerability.

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