Malicious Code Vulnerability in init-router Package

init-router Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192803: Malicious code in init-router (npm). Affects init-router versions 2.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 init-router package is a Node.js library used for managing routing in applications. It allows developers to define routes and handle requests efficiently. However, this package has been identified to contain malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the init-router package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was reported by ReversingLabs, and it affects version 2.0.1 of the package. Users of this package should be aware of the potential ramifications, including loss of data integrity and exposure to further attacks.

How To Fix

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

npm uninstall init-router

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 init-router package from your project until a secure version is released. You can do this by running the following command: npm uninstall init-router. Consider using alternative routing packages that are known to be secure.

Conclusion

The init-router package has been identified to contain malicious code that poses significant security risks. It is crucial for developers using this package to update to a secure version or consider alternative solutions to protect their applications from potential threats.

See every vulnerability recorded for init-router →

Share this vulnerability

FAQ

The init-router package is a Node.js library that helps developers manage routing in their applications.

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Yes, you can temporarily uninstall the init-router package or use an alternative routing library until a secure version is available.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

How To Fix

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

npm uninstall init-router

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