Critical Malicious Code Vulnerability in flaskbase Package

flaskbase Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20685: Malicious code in flaskbase (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 flaskbase package is a Node.js library designed for building web applications using Flask-like features. It provides developers with tools to create robust and scalable applications. However, this package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the flaskbase package arises from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to address this issue promptly.

How To Fix

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

npm uninstall flaskbase

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, users can avoid using the flaskbase package until a secure version is released. Additionally, consider using alternative packages that offer similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the flaskbase package highlights the importance of maintaining secure coding practices and regularly monitoring dependencies. Users are urged to update their packages and consider alternative solutions until a secure version is available.

See every vulnerability recorded for flaskbase →

Share this vulnerability

FAQ

Flaskbase is a Node.js library that helps developers build web applications with features similar to Flask, providing tools for creating scalable applications.

The malicious code in flaskbase can lead to unauthorized access and data breaches, posing serious security threats to applications using this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can help identify if your application is at risk.

Yes, you can temporarily avoid using the flaskbase package until a secure version is released. Consider using alternative packages that provide similar functionality.

Regularly check for updates to your packages and utilize tools like Vulert to monitor your dependencies for any newly discovered vulnerabilities.

How To Fix

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

npm uninstall flaskbase

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