Malicious Code Detected in bizdiary Package - Security Alert

bizdiary Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15766: Malicious code in bizdiary (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 bizdiary package is an npm library designed to assist users in managing their daily activities and tasks efficiently. It offers features such as task scheduling, reminders, and progress tracking. However, recent findings have revealed that this package contains malicious code, posing a significant threat to users who rely on it for their daily productivity.

Vulnerability Detail

The vulnerability in the bizdiary package stems from the inclusion of malicious code that can compromise user data and system integrity. This code was introduced in all versions starting from 0, making every installation of the package potentially harmful. Users may experience unauthorized access to their data, data theft, or even system corruption as a result of this vulnerability.

How To Fix

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

npm uninstall bizdiary

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

If you cannot update the package immediately, consider removing it from your project until a secure version is released. You can do this by running: npm uninstall bizdiary. Additionally, monitor your application for any suspicious activity.

Conclusion

The discovery of malicious code in the bizdiary package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to secure their applications by updating or removing the affected package. Regular monitoring and updates are essential to maintaining software security.

See every vulnerability recorded for bizdiary →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access to user data and may compromise system security.

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

Immediately uninstall the package and monitor your application for any unusual behavior. Consider updating to a patched version once available.

While specific exploits have not been detailed, the potential for data theft and system compromise is significant.

Utilize tools like Vulert to receive real-time alerts on vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall bizdiary

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