Malicious Code Detected in bullyshitty (npm) - Version 3.0.0

bullyshitty Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6383: Malicious code in bullyshitty (npm). Affects bullyshitty versions 3.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'bullyshitty' package is an npm module that may be used for various functionalities in JavaScript applications. However, it has been identified as malicious in version 3.0.0 due to its ability to communicate with domains linked to harmful activities and execute commands that can compromise system integrity. This vulnerability raises significant concerns for developers relying on this package for their projects.

Vulnerability Detail

The vulnerability in the 'bullyshitty' package arises from its malicious behavior, which includes communicating with a domain associated with malicious activities and executing harmful commands. This behavior can lead to unauthorized access, data breaches, and potential system compromise, making it critical for users of this package to take immediate action to mitigate risks.

How To Fix

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

npm uninstall bullyshitty

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 replacing 'bullyshitty' with a safer alternative package that provides similar functionality. Review your project's dependencies and ensure that you are not relying on any malicious packages. Regularly audit your package-lock.json file to identify and address vulnerabilities.

Conclusion

The identification of malicious code in the 'bullyshitty' package underscores the importance of vigilance in managing open-source dependencies. Developers should take immediate action to remove this package and consider safer alternatives to protect their applications from potential threats.

See every vulnerability recorded for bullyshitty →

Share this vulnerability

FAQ

The 'bullyshitty' package is an npm module that has been identified as malicious due to its harmful behavior, including executing commands and communicating with malicious domains.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without needing to sign up.

If you have installed 'bullyshitty', you should uninstall it immediately using 'npm uninstall bullyshitty' and look for alternative packages.

While specific alternatives depend on the functionality you need, consider searching the npm registry for packages that offer similar features without the associated risks.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall bullyshitty

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