Critical Malicious Code Vulnerability in compliancereadserv Package

compliancereadserv Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17451: Malicious code in compliancereadserv (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 compliancereadserv package is an npm library designed to facilitate compliance reading services. It offers functionalities that allow developers to integrate compliance checks into their applications. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the compliancereadserv package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall compliancereadserv

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 removing the compliancereadserv package from your project until a secure version is released. You can do this by running: npm uninstall compliancereadserv.

Conclusion

The compliancereadserv package has been identified as containing malicious code, posing serious security risks to applications. Users are urged to take immediate action by removing the package and monitoring their applications for any potential vulnerabilities. Utilizing tools like Vulert can aid in maintaining security in open-source projects.

See every vulnerability recorded for compliancereadserv →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that use this package.

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

Currently, there is no patched version available. It is recommended to remove the package or find a secure alternative.

You should immediately uninstall the package and assess your application for any potential security breaches.

Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights without requiring access to your code.

How To Fix

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

npm uninstall compliancereadserv

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