Malicious Code Detected in corelyzer: A Critical npm Vulnerability

corelyzer Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17581: Malicious code in corelyzer (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

The corelyzer package is an npm library designed to assist developers in analyzing and visualizing code quality metrics. It offers features such as performance tracking and code complexity analysis. However, it has been identified as containing malicious code, which poses significant security risks to applications relying on this package.

Vulnerability Detail

The vulnerability in the corelyzer package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originated from the package's version 0 and has been flagged as a serious threat by security researchers.

How To Fix

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

npm uninstall corelyzer

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 measure, you can avoid using the corelyzer package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The corelyzer package has been identified as containing malicious code, posing significant security risks to applications. It is crucial for developers to remove this package and seek alternatives to ensure the safety of their software. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.

See every vulnerability recorded for corelyzer →

Share this vulnerability

FAQ

Corelyzer is an npm package used for analyzing and visualizing code quality metrics in software development.

The malicious code can lead to unauthorized access and potential data breaches within applications that utilize the corelyzer package.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including those in corelyzer.

The best mitigation strategy is to remove the corelyzer package and replace it with a secure alternative until a patched version is released.

Detailed information about this vulnerability can be found on the GitHub repository of the malicious packages project.

How To Fix

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

npm uninstall corelyzer

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