Malicious Code Detected in Algodoo Package - MAL-2025-14298

algodoo Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14298: Malicious code in algodoo (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

Algodoo is an interactive physics simulation software that allows users to create and explore physics experiments in a virtual environment. It is widely used for educational purposes and offers features such as 2D simulations, a user-friendly interface, and the ability to share creations. However, the package has been found to contain malicious code, posing a significant risk to users who install it.

Vulnerability Detail

The vulnerability in the Algodoo package stems from the inclusion of malicious code that can compromise the security of systems where it is installed. 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, making it critical for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall algodoo

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, users can avoid using the Algodoo package until a secure version is released. It is advisable to monitor the package's repository for updates or consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the Algodoo package poses a serious threat to users. Immediate action is required to remove the package and safeguard systems from potential harm. Users are encouraged to stay informed about updates and consider alternative solutions until a secure version is available.

See every vulnerability recorded for algodoo →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to user systems and may lead to data theft or other harmful actions.

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.

It is recommended to uninstall the Algodoo package immediately to mitigate any potential risks associated with the malicious code.

Yes, there are several alternatives available that provide similar physics simulation functionalities without the associated risks. Research and choose a reputable package.

As of now, there is no information regarding a patch. Users should monitor the package repository for any updates or announcements regarding a secure version.

How To Fix

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

npm uninstall algodoo

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