Malicious Code Detected in next-minimal-server: A Critical Security Alert

next-minimal-server Updated 02 Oct 2025

Summary

26/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6260: Malicious code in next-minimal-server (npm). Affects next-minimal-server versions >= 10.0.1. 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 'next-minimal-server' package is a Node.js server framework designed for minimalistic web applications. It is utilized for its simplicity and ease of integration with various front-end frameworks. However, version 10.0.1 has been flagged for malicious behavior, specifically for communicating with a domain associated with harmful activities, which poses significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability in 'next-minimal-server' arises from its ability to communicate with a malicious domain and execute commands that can compromise the security of the host system. This behavior was identified by the OpenSSF Package Analysis project, which found that the package version 10.0.1 could potentially lead to unauthorized access, data breaches, and other malicious activities. The origin of this vulnerability is linked to the package's design, which allows it to connect to external domains without sufficient security checks.

How To Fix

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

npm uninstall next-minimal-server

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, you can remove the 'next-minimal-server' package from your project until a secure version is released. You can do this by running the command: 'npm uninstall next-minimal-server'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the 'next-minimal-server' package version 10.0.1 highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability.

See every vulnerability recorded for next-minimal-server →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain linked to malicious activities and executing harmful commands.

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

If an immediate update is not possible, consider removing the package or using an alternative until a secure version is available.

While specific exploits have not been detailed, the potential for unauthorized access and data breaches exists due to the malicious behavior of the package.

Regularly check for updates in your dependencies and utilize tools like Vulert to monitor vulnerabilities in real-time.

How To Fix

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

npm uninstall next-minimal-server

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