Critical Malicious Code Vulnerability in node-calculator-fa00 Package

node-calculator-fa00 Updated 21 Nov 2025

Summary

20/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190583: Malicious code in node-calculator-fa00 (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 node-calculator-fa00 package is an npm library designed for performing basic mathematical calculations. It is intended for developers looking to integrate simple calculator functionalities into their applications. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the node-calculator-fa00 package. This code can compromise any computer that has the package installed, granting unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to complete control of the affected system by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall node-calculator-fa00

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Users should ensure that they do not run any applications that depend on node-calculator-fa00 until it has been completely uninstalled.

Conclusion

The node-calculator-fa00 package poses a critical security risk due to embedded malicious code. Immediate action is required to uninstall the package and secure any compromised information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for node-calculator-fa00 →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any sensitive information that may have been compromised.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

No, there is currently no patched version available for this package.

Failing to remove the package could lead to unauthorized access to your system and potential data breaches.

Yes, you can explore other calculator packages that do not have known vulnerabilities.

How To Fix

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

npm uninstall node-calculator-fa00

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