Malicious Code Detected in cantynovi Package - Immediate Action Required

cantynovi Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16501: Malicious code in cantynovi (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cantynovi package is a Node.js library designed for specific functionalities within the npm ecosystem. It is utilized by developers to streamline certain tasks in their applications. However, this package has been found to contain malicious code, posing significant risks to users and their applications. The vulnerability affects all versions of the package, making it critical for users to take immediate action.

Vulnerability Detail

The vulnerability in the cantynovi package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. Users of this package are at risk of having their applications manipulated or their data compromised due to this vulnerability.

How To Fix

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

npm uninstall cantynovi

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 workaround, users can replace the cantynovi package with an alternative library that provides similar functionality without the associated risks. Ensure to review the alternatives thoroughly before implementation.

Conclusion

The discovery of malicious code in the cantynovi package poses a significant threat to users and their applications. Immediate action is required to uninstall the package and seek alternatives to ensure the security of your projects. Stay vigilant and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for cantynovi →

Share this vulnerability

FAQ

The cantynovi package is a Node.js library used in npm projects for specific functionalities, but it has been compromised with malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

You should immediately uninstall the cantynovi package and look for alternative libraries to replace its functionality.

As of now, there is no patched version available. It is recommended to remove the package entirely.

Using the cantynovi package can lead to unauthorized access, data breaches, and exploitation of your application due to the embedded malicious code.

How To Fix

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

npm uninstall cantynovi

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