Critical Malicious Code Vulnerability in cscribe Package

cscribe Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17775: Malicious code in cscribe (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The cscribe package is a JavaScript library used in Node.js applications for creating and managing text-based content. It is designed to facilitate the writing process by providing various utilities for text manipulation. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the cscribe package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or disrupt normal application functionality. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall cscribe

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 cscribe package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall cscribe'. Additionally, monitor your package dependencies regularly for any updates or security advisories.

Conclusion

The cscribe package has been identified to contain malicious code, which poses serious security threats to applications that utilize it. Developers are urged to update or remove the package to mitigate risks. Regular monitoring of dependencies and utilizing tools like Vulert can help maintain application security.

See every vulnerability recorded for cscribe →

Share this vulnerability

FAQ

The cscribe package is used for creating and managing text-based content in Node.js applications, providing utilities for text manipulation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected. Visit the Vulert playground at Vulert Scanner for a quick assessment without signup.

If an immediate update is not possible, consider removing the cscribe package from your project as a temporary measure until a secure version is available.

Detailed information about the vulnerability can be found in the official GitHub repository of the cscribe package and through security advisories related to npm packages.

Using the compromised cscribe package can lead to unauthorized access to sensitive data, execution of arbitrary commands, and disruption of application functionality, posing significant security risks.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall cscribe

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