Malicious Code Detected in areology-biogeochemistry-non-blocking-commitlint Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14813: Malicious code in areology-biogeochemistry-non-blocking-commitlint (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 areology-biogeochemistry-non-blocking-commitlint package is an npm module designed to facilitate non-blocking commit linting for projects related to biogeochemistry. It is intended to enhance the development workflow by ensuring code quality through commit message validation. However, this package has been found to contain malicious code, posing significant risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the areology-biogeochemistry-non-blocking-commitlint package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was identified by security researchers and is documented in the Open Source Vulnerability database.

How To Fix

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

npm uninstall areology-biogeochemistry-non-blocking-commitlint

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 areology-biogeochemistry-non-blocking-commitlint package until a safe version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the areology-biogeochemistry-non-blocking-commitlint package highlights the importance of vigilance in managing open-source dependencies. Users should take immediate action to remove the package and monitor for updates to ensure the security of their applications.

See every vulnerability recorded for areology-biogeochemistry-non-blocking-commitlint →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to your application, leading to data breaches or other security issues.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

The best way to mitigate risks is to remove the affected package and monitor for any updates or patches from the maintainers.

Immediately remove the package from your project and consider using alternative packages that do not have known vulnerabilities.

Currently, there is no patch available. Users are advised to remove the package until a secure version is released.

How To Fix

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

npm uninstall areology-biogeochemistry-non-blocking-commitlint

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