Malicious Code Detected in bisocie Package - Security Alert

bisocie Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15735: Malicious code in bisocie (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 bisocie package is a Node.js library available through the npm ecosystem. It is designed for specific functionalities that may include data manipulation or API interactions. However, it has been identified to contain malicious code, posing significant risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The bisocie package has been found to contain malicious code that can compromise the security of applications using it. This vulnerability originated from the package itself, which was likely introduced during development or through malicious intent. The ramifications of this vulnerability include potential data theft, unauthorized access to user information, and exploitation of the affected systems. It is crucial for developers to be aware of this issue to mitigate risks associated with using this package.

How To Fix

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

npm uninstall bisocie

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 measure, you can avoid using the bisocie package altogether and look for alternative packages that provide similar functionality without the associated risks. Ensure to review the security history of any alternative packages before implementation.

Conclusion

The bisocie package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Developers are urged to uninstall the package and seek alternatives to safeguard their applications. Regular monitoring and updates are essential to maintain security in software development.

See every vulnerability recorded for bisocie →

Share this vulnerability

FAQ

The bisocie package is a Node.js library used for various functionalities in applications, but it has been flagged for containing malicious code.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without any signup.

If you are using bisocie, it is advised to uninstall the package immediately and look for alternatives. Run 'npm uninstall bisocie' to remove it from your project.

Currently, there is no patched version available for bisocie. It is best to remove the package and seek alternatives.

To prevent similar vulnerabilities, regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review package security advisories.

How To Fix

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

npm uninstall bisocie

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