Malicious Code Detected in algerb Package - Security Alert

algerb Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14297: Malicious code in algerb (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The algerb package is an npm library designed for algebraic computations, providing users with functions to perform various mathematical operations. However, it has been found to contain malicious code, posing significant security risks to applications that utilize this package. Users rely on algerb for its functionality, but the presence of this vulnerability compromises the integrity and security of their applications.

Vulnerability Detail

The vulnerability in the algerb package stems from the inclusion of malicious code that can execute harmful actions on the user's system. This code can potentially lead to data breaches, unauthorized access, or other malicious activities. The issue was identified in version 0 and has been documented as MAL-2025-14297. Users who have installed this package are at risk, and it is crucial to address this vulnerability promptly to prevent exploitation.

How To Fix

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

npm uninstall algerb

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 algerb package altogether and seek alternative libraries that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The discovery of malicious code in the algerb package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to remove the affected package and monitor their applications for vulnerabilities to maintain security.

See every vulnerability recorded for algerb →

Share this vulnerability

FAQ

The algerb package is an npm library used for algebraic computations, offering various mathematical functions.

The malicious code can execute harmful actions on the user's system, potentially leading to data breaches or unauthorized access.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should remove the algerb package from your project and update to a patched version if available.

Vulert monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json, ensuring your applications remain secure.

How To Fix

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

npm uninstall algerb

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