Critical Malicious Code Vulnerability in node-mongo-orm Package

node-mongo-orm Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5940: Malicious code in node-mongo-orm (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

node-mongo-orm is an npm package designed to provide a simple and efficient Object-Relational Mapping (ORM) interface for MongoDB. It allows developers to interact with MongoDB databases using JavaScript objects, streamlining database operations. However, this package has been identified to contain malicious code, posing significant security risks to any application utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the node-mongo-orm package. This code can compromise any computer that has the package installed, leading to unauthorized access and control over the system. The ramifications include potential data breaches, loss of sensitive information, and the risk of further malware installation. The vulnerability is classified under CWE-506, indicating that the code appears to be malicious in nature.

How To Fix

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

npm uninstall node-mongo-orm

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 ORM package that does not have known vulnerabilities. Additionally, ensure that all secrets and keys stored on the affected computer are rotated immediately to mitigate any potential risks.

Conclusion

The node-mongo-orm package contains a critical vulnerability due to embedded malicious code, which poses significant risks to any system using it. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor for updates and consider alternative packages.

See every vulnerability recorded for node-mongo-orm →

Share this vulnerability

FAQ

node-mongo-orm is an npm package that provides an Object-Relational Mapping interface for MongoDB, allowing developers to interact with databases using JavaScript objects.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

If you have the node-mongo-orm package installed, you should remove it immediately and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available for the node-mongo-orm package. It is recommended to monitor the package's repository for any updates.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall node-mongo-orm

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