Malicious Code Detected in bad-spy-shell-report-assert Package

bad-spy-shell-report-assert Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15329: Malicious code in bad-spy-shell-report-assert (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 bad-spy-shell-report-assert package is an npm module designed for reporting assertions in shell environments. It is utilized by developers to streamline testing processes and enhance debugging capabilities. However, this package has been found to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the bad-spy-shell-report-assert package. This code can potentially compromise the security of applications, leading to unauthorized access, data breaches, or system manipulation. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall bad-spy-shell-report-assert

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 remove the bad-spy-shell-report-assert package from your project by executing the following command: npm uninstall bad-spy-shell-report-assert. This will prevent any malicious code from executing while you seek a safer alternative.

Conclusion

The bad-spy-shell-report-assert package contains malicious code that poses significant security risks. Users are advised to update or remove the package to protect their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for bad-spy-shell-report-assert →

Share this vulnerability

FAQ

It is an npm module used for reporting assertions in shell environments, aiding developers in testing and debugging.

The malicious code was found in the package from its initial version, indicating a deliberate inclusion by the package maintainer.

Using this package can lead to unauthorized access, data breaches, and potential manipulation of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall bad-spy-shell-report-assert

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