Malicious Code Detected in cuttlab Package - Security Alert

cuttlab Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17848: Malicious code in cuttlab (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 cuttlab package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and various features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the cuttlab package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue affects all versions of the package starting from its introduction, 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 cuttlab

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 can remove the cuttlab package from their project dependencies and replace it with an alternative package that offers similar functionality without the associated risks. This can be done by executing the command: npm uninstall cuttlab.

Conclusion

The cuttlab package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Users are strongly encouraged to remove this package and seek alternatives to ensure the security of their applications.

See every vulnerability recorded for cuttlab →

Share this vulnerability

FAQ

The cuttlab package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. By utilizing the Vulert playground, you can check if your application is affected without any signup.

You should immediately remove the cuttlab package from your project and look for alternative packages that do not pose security risks.

Currently, there is no patch available for the cuttlab package. Users are advised to uninstall it until a secure version is released.

Using the cuttlab package can lead to unauthorized access, data breaches, and other harmful actions within your application, compromising its security.

How To Fix

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

npm uninstall cuttlab

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