Malicious Code Injection in ariel-spawn-commitlint-config-angular-cressida Package

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-139596: Malicious code in ariel-spawn-commitlint-config-angular-cressida (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 ariel-spawn-commitlint-config-angular-cressida package is part of the npm ecosystem and is designed to facilitate commit linting in Angular projects. It aims to enforce consistent commit message formats, which is crucial for maintaining a clean project history. However, this package has been compromised, making it susceptible to malicious activities that can affect developers and their projects.

Vulnerability Detail

The vulnerability originates from a malicious code injection within the ariel-spawn-commitlint-config-angular-cressida package. This package is linked to a broader campaign that floods the npm registry with derivative packages containing autopublish scripts. These scripts are designed to modify the package.json file, removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially harming developer reputations and project integrity.

How To Fix

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

npm uninstall ariel-spawn-commitlint-config-angular-cressida

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 package for commit linting that has not been flagged for malicious activity. Ensure to review the package's reputation and community feedback before integrating it into your project.

Conclusion

The ariel-spawn-commitlint-config-angular-cressida package has been identified as containing malicious code that can compromise the integrity of projects using it. Developers are urged to remove this package and consider alternatives while monitoring for updates and patches.

See every vulnerability recorded for ariel-spawn-commitlint-config-angular-cressida →

Share this vulnerability

FAQ

It is an npm package designed to enforce commit message conventions in Angular projects.

The package was compromised as part of a malicious campaign that aimed to inflate developer reputation scores through the creation of numerous derivative packages.

The risks include potential pollution of the npm registry, loss of developer reputation, and the possibility of introducing further vulnerabilities into your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup at Vulert Scanner.

If immediate removal is not possible, consider using an alternative package for commit linting and monitor your project for any unusual behavior.

How To Fix

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

npm uninstall ariel-spawn-commitlint-config-angular-cressida

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.