Malicious Code Vulnerability in crankcms (npm)

crankcms Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17656: Malicious code in crankcms (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 crankcms package is a content management system designed for building and managing web applications. It offers features such as templating, routing, and database integration, making it a popular choice among developers. However, recent findings have revealed that crankcms contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in crankcms arises from the inclusion of malicious code within the package. This code can potentially compromise the security of applications that utilize crankcms, leading 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 address this vulnerability promptly.

How To Fix

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

npm uninstall crankcms

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, users may consider removing the crankcms package from their project until a secure version is released. This can be done using the command: npm uninstall crankcms. Additionally, review your application's dependencies to ensure no other packages are affected by similar vulnerabilities.

Conclusion

The crankcms package has been identified to contain malicious code, posing significant risks to users and their applications. It is crucial to update the package or consider workarounds to mitigate potential threats. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for crankcms →

Share this vulnerability

FAQ

Crankcms is a content management system for building and managing web applications, offering various features for developers.

The malicious code can lead to unauthorized access and potential data breaches, posing serious security risks to applications using the 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.

Users should check the package repository for any updates or patches that may have been released to address the vulnerability.

As a temporary measure, consider uninstalling the crankcms package and reviewing your dependencies for similar vulnerabilities.

How To Fix

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

npm uninstall crankcms

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