Malicious Code Detected in cicada-render Package - Security Alert

cicada-render Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17016: Malicious code in cicada-render (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 cicada-render package is an npm library designed for rendering tasks in web applications. It is utilized for its efficiency and ease of integration into various projects. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The cicada-render package has been identified to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originates from the package itself, which was found to introduce harmful functionalities that could lead to unauthorized access, data breaches, or other malicious activities. Developers using this package are at risk of exposing their applications to potential attacks.

How To Fix

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

npm uninstall cicada-render

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 measure, consider removing the cicada-render package from your project until a secure version is available. You can do this by executing the command: npm uninstall cicada-render.

Conclusion

The cicada-render package has been found to contain malicious code, posing serious security risks to applications that utilize it. It is essential for developers to update or remove the package to protect their applications from potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for cicada-render →

Share this vulnerability

FAQ

cicada-render is an npm package used for rendering tasks in web applications, known for its efficiency.

The malicious code was identified through security audits and reports from security tools like Amazon Inspector.

Using the compromised package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

If immediate updates are not possible, consider removing the package or implementing additional security measures to mitigate risks.

Related vulnerabilities

Recent vulnerabilities recorded for cicada-render.

How To Fix

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

npm uninstall cicada-render

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