Malicious Code Detected in node-calculator-d234 Package - Security Alert

node-calculator-d234 Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190541: Malicious code in node-calculator-d234 (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

The node-calculator-d234 package is a JavaScript library available on npm, designed for performing basic arithmetic calculations. It is commonly used in web applications to provide users with a simple calculator interface. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the node-calculator-d234 package. This code can potentially compromise the security of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The issue was reported by Amazon Inspector, which detected the malicious code during a routine security assessment.

How To Fix

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

npm uninstall node-calculator-d234

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, consider using an alternative package that provides similar functionality without the associated risks. You can search for other calculator libraries on npm that have a good reputation and positive reviews.

Conclusion

The discovery of malicious code in the node-calculator-d234 package highlights the importance of regularly auditing dependencies in your projects. By promptly addressing this vulnerability, you can protect your applications from potential security threats.

See every vulnerability recorded for node-calculator-d234 →

Share this vulnerability

FAQ

node-calculator-d234 is a JavaScript library used for performing basic arithmetic calculations in web applications.

The malicious code was detected by Amazon Inspector during a security assessment of the package.

Using the compromised package can lead to unauthorized access, data breaches, and other malicious activities within your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have used this package, you should uninstall it immediately and look for a secure alternative to ensure your application's safety.

How To Fix

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

npm uninstall node-calculator-d234

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