Malicious Code Detected in byte-void-mock-awk-slow Package

byte-void-mock-awk-slow Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16403: Malicious code in byte-void-mock-awk-slow (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The byte-void-mock-awk-slow package is an npm library designed for specific mock functionalities in JavaScript applications. It is often utilized by developers for testing and development purposes. However, this package has been identified to contain malicious code, posing a significant risk to applications that depend on it.

Vulnerability Detail

The vulnerability in the byte-void-mock-awk-slow 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 harmful actions within the application environment. The malicious nature of this code was discovered by security researchers, raising concerns about the integrity of the package and its potential impact on users.

How To Fix

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

npm uninstall byte-void-mock-awk-slow

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, consider using alternative packages that provide similar functionalities without the associated risks. Always review the security status of packages before integrating them into your projects.

Conclusion

The byte-void-mock-awk-slow package has been found to contain malicious code, posing serious security risks to applications that utilize it. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for byte-void-mock-awk-slow →

Share this vulnerability

FAQ

It is an npm library used for mock functionalities in JavaScript applications.

The malicious code was identified by security researchers during routine checks of npm packages.

Using this package can lead to unauthorized access and potential data breaches in your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

Uninstall the package immediately and consider using alternative libraries that are secure.

How To Fix

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

npm uninstall byte-void-mock-awk-slow

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