Malicious Code Detected in cressida-commitlint-config-angular-proteomics-development Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17679: Malicious code in cressida-commitlint-config-angular-proteomics-development (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The cressida-commitlint-config-angular-proteomics-development package is designed for configuring commit linting in Angular projects. It helps maintain consistent commit messages by enforcing rules. However, this package has been compromised, containing malicious code that can pose significant risks to users and their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cressida-commitlint-config-angular-proteomics-development package. This malicious code can potentially lead to unauthorized access, data breaches, or the execution of harmful actions within the user's environment. The package is affected from version 0 onwards, making all versions vulnerable.

How To Fix

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

npm uninstall cressida-commitlint-config-angular-proteomics-development

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 an alternative commit linting configuration package that is known to be secure until the vulnerability is addressed in the affected package.

Conclusion

The cressida-commitlint-config-angular-proteomics-development package has been identified as containing malicious code, posing significant risks to users. It is crucial to uninstall the package and consider alternatives until a secure version is released. Utilizing tools like Vulert can help monitor and manage vulnerabilities in your projects effectively.

See every vulnerability recorded for cressida-commitlint-config-angular-proteomics-development →

Share this vulnerability

FAQ

It is a package used to configure commit linting for Angular projects, ensuring that commit messages adhere to specified rules.

The specific nature of the malicious code has not been disclosed, but it poses risks such as unauthorized access and potential data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By uploading your package-lock.json file, you can check for vulnerabilities in real-time.

The best mitigation strategy is to uninstall the affected package and consider using a secure alternative until a patched version is released.

Immediately uninstall the package and review your project for any potential impacts caused by the malicious code.

How To Fix

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

npm uninstall cressida-commitlint-config-angular-proteomics-development

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