Critical Malicious Activity Detected in conformance-test Package

conformance-test Updated 02 Oct 2025

Summary

28/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6706: Malicious code in conformance-test (npm). Affects conformance-test versions >= 1.0.0. 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 conformance-test package is an npm library designed for testing and validating compliance with certain standards. It is widely used in various applications for ensuring that code meets specific criteria. However, this package has been found to communicate with a domain linked to malicious activities, raising significant security concerns for users and developers relying on it.

Vulnerability Detail

The vulnerability in the conformance-test package stems from its communication with a domain associated with malicious activity. This could potentially lead to data breaches, unauthorized access, or the execution of harmful code within applications that utilize this package. The issue was introduced in version 1.0.0, and it poses a serious risk to any application that integrates this package, as it may inadvertently expose sensitive information or compromise system integrity.

How To Fix

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

npm uninstall conformance-test

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 conformance-test package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall conformance-test'. Additionally, monitor your application for any suspicious activity during this period.

Conclusion

The conformance-test package has a critical vulnerability due to its communication with a malicious domain. Users are advised to update the package as soon as a patched version is available, or to remove it temporarily to mitigate risks. Regular monitoring and utilizing tools like Vulert can help ensure the security of your applications.

See every vulnerability recorded for conformance-test →

Share this vulnerability

FAQ

The conformance-test package is an npm library used for testing compliance with specific standards in software applications.

The package has been found to communicate with a domain linked to malicious activities, which could lead to data breaches or unauthorized access.

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

Currently, there is no specific patch version mentioned. It is crucial to keep an eye on the package repository for updates that address this vulnerability.

If you cannot update the package right away, consider removing it from your project and monitoring for any suspicious activity as a temporary measure.

How To Fix

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

npm uninstall conformance-test

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