Malicious Code Detected in Cakelinge Package - MAL-2025-16435

cakelinge Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16435: Malicious code in cakelinge (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

Cakelinge is an npm package designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the cakelinge package is characterized by the presence of malicious code that can compromise the security of applications utilizing this package. This issue originated from the package's codebase, which was found to be intentionally harmful. The ramifications of this vulnerability include potential data breaches, unauthorized access to sensitive information, and the ability for attackers to execute arbitrary code within affected applications.

How To Fix

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

npm uninstall cakelinge

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, you can prevent the use of the cakelinge package by removing it from your package.json file and running npm install to update your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.

Conclusion

The discovery of malicious code in the cakelinge package poses a serious threat to applications that utilize it. Developers are advised to take immediate action by removing the package and monitoring their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential in maintaining application security.

See every vulnerability recorded for cakelinge →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you are using the cakelinge package, you should remove it from your project and replace it with a secure alternative or update to a patched version if available.

The risks include potential data breaches, unauthorized access to sensitive information, and the execution of arbitrary code within your applications.

Vulert monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file, providing real-time insights into potential security issues.

How To Fix

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

npm uninstall cakelinge

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