Malicious Code Detected in Freeplane Package - Security Alert

freeplane Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20951: Malicious code in freeplane (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Freeplane is an open-source software application that allows users to create and manage mind maps. It is widely used for brainstorming, project planning, and knowledge management. However, recent findings have revealed that the package contains malicious code, posing significant security risks to users and their data.

Vulnerability Detail

The vulnerability in the Freeplane package stems from the inclusion of malicious code that can compromise user systems. This code may lead to unauthorized access, data theft, or other harmful actions. The issue was introduced in version 0 and affects all subsequent versions. Users of Freeplane are at risk of exploitation if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall freeplane

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 an immediate update is not feasible, users can temporarily avoid using the Freeplane package until a secure version is available. Additionally, consider using alternative mind mapping tools that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the Freeplane package highlights the importance of maintaining updated software and being vigilant about security vulnerabilities. Users must take immediate action to update their packages and consider using tools like Vulert for ongoing monitoring.

See every vulnerability recorded for freeplane →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches, compromising user security.

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

Yes, users are advised to update to the latest version of Freeplane to mitigate the risk associated with the malicious code.

As a temporary measure, refrain from using the Freeplane package and consider alternative tools until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert users in real-time for any open-source vulnerabilities in their software.

Related vulnerabilities

Recent vulnerabilities recorded for freeplane.

How To Fix

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

npm uninstall freeplane

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