Critical Malicious Code Vulnerability in byhand Package (npm)

byhand Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16396: Malicious code in byhand (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 byhand package is a JavaScript library available through the npm ecosystem, designed for various utility functions in web development. It is widely used due to its simplicity and ease of integration into projects. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the byhand package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, or other harmful activities within the affected systems. The malicious nature of this vulnerability is particularly concerning as it can operate without the user's knowledge, making it a severe threat to application integrity.

How To Fix

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

npm uninstall byhand

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, you can avoid using the byhand package altogether and look for alternative libraries that provide similar functionality without the associated risks. Additionally, you can implement security measures such as code reviews and dependency audits to mitigate potential threats.

Conclusion

The discovery of malicious code within the byhand package highlights the importance of maintaining vigilance in software dependencies. Users are encouraged to update their packages promptly and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for byhand →

Share this vulnerability

FAQ

The byhand package is a JavaScript library used for utility functions in web development, available through the npm ecosystem.

The malicious code in the byhand package was identified through security audits conducted by researchers, including those from Amazon Inspector.

Using the byhand package with the malicious code can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider implementing security measures such as code reviews and using alternative libraries to minimize risk.

How To Fix

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

npm uninstall byhand

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