Malicious Code Detected in Bussocial Package - Security Alert

bussocial Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16363: Malicious code in bussocial (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 Bussocial package is an npm library designed for social media automation and engagement. It offers functionalities such as scheduling posts, managing interactions, and analyzing social media metrics. However, its recent discovery of malicious code poses significant security risks to users and their applications.

Vulnerability Detail

The Bussocial package has been identified to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the package's codebase, which was intentionally altered to include harmful scripts. The ramifications of this vulnerability include unauthorized access to user data, potential data breaches, and exploitation of the affected systems. It is crucial for developers to be aware of this issue to prevent further exploitation.

How To Fix

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

npm uninstall bussocial

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, consider using alternative packages for social media automation that have been vetted for security. Ensure to review the package's code and community feedback before integrating it into your project.

Conclusion

The Bussocial package has been flagged for containing malicious code, posing serious security risks. Users are advised to remove the package and seek alternatives while remaining vigilant for updates and patches. Utilizing tools like Vulert can help in monitoring vulnerabilities in real-time.

See every vulnerability recorded for bussocial →

Share this vulnerability

FAQ

Bussocial is an npm package used for automating social media tasks, such as scheduling posts and managing interactions.

The malicious code can potentially allow unauthorized access to user data and compromise application security.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Remove the Bussocial package from your project immediately and look for alternative solutions.

Currently, there are no patches available for Bussocial. Users should monitor the package repository for any future updates.

How To Fix

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

npm uninstall bussocial

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