Malicious Code Detected in example-backend-next Package

example-backend-next Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20031: Malicious code in example-backend-next (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 example-backend-next package is an npm library designed for building backend applications using Next.js. It provides essential functionalities for developers to create efficient and scalable server-side applications. However, this package has been identified to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the example-backend-next package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code may lead to unauthorized access, data breaches, or other harmful actions that could severely impact the integrity and confidentiality of user data. Users of this package are at risk from the moment they introduce it into their projects, as the malicious code is executed within their application environment.

How To Fix

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

npm uninstall example-backend-next

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 alternative packages that provide similar functionalities without the associated risks. Review your project's dependencies and assess if you can replace example-backend-next with a more secure option.

Conclusion

The example-backend-next package has been identified as containing malicious code, posing significant risks to users. It is crucial to remove this package from your projects and monitor for any updates or alternatives. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for example-backend-next →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within your application, potentially leading to data breaches or system compromises.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Immediately remove the package from your project and look for a secure alternative or a patched version if available.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Ignoring this vulnerability could lead to severe security breaches, including unauthorized access to sensitive data and potential exploitation of your application.

How To Fix

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

npm uninstall example-backend-next

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