Malicious Code Detected in render-stage Package - npm Vulnerability

render-stage Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191524: Malicious code in render-stage (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The render-stage package is a Node.js library used in various applications for rendering stages in web development. It is designed to streamline the rendering process, providing developers with tools to create dynamic and interactive user interfaces. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the render-stage package, which has been identified to contain malicious code. This code can potentially compromise the security of applications by allowing unauthorized access, data manipulation, or other malicious activities. The issue was reported by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security flaws.

How To Fix

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

npm uninstall render-stage

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 render-stage package from your project if it is not critical. You can do this by running the command: 'npm uninstall render-stage'. Alternatively, you can replace it with a similar package that does not have known vulnerabilities.

Conclusion

The render-stage package has been found to contain malicious code, posing a significant security risk to applications that utilize it. It is crucial for developers to update the package to a secure version or consider alternative solutions to mitigate potential threats. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for render-stage →

Share this vulnerability

FAQ

The render-stage package is a Node.js library used for rendering stages in web applications, facilitating dynamic user interface creation.

The malicious code was identified by Amazon Inspector, which conducts security assessments on open-source packages.

Using the compromised package can lead to unauthorized access, data breaches, and potential exploitation of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If immediate updates are not possible, consider removing the package or replacing it with a secure alternative until a fix can be applied.

How To Fix

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

npm uninstall render-stage

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