Malicious Code Detected in celeste-radiant-yaml-command Package

celeste-radiant-yaml-command Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16705: Malicious code in celeste-radiant-yaml-command (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 celeste-radiant-yaml-command package is an npm module designed for handling YAML commands in a user-friendly manner. It allows developers to easily parse and manipulate YAML files within their applications. However, this package has been found to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the celeste-radiant-yaml-command package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The vulnerability affects all versions starting from 0, making it critical for users to take immediate action to mitigate the risks associated with this package.

How To Fix

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

npm uninstall celeste-radiant-yaml-command

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 isolate the use of this package in a controlled environment and monitor its behavior closely. However, this is not a long-term solution, and the package should be removed as soon as possible.

Conclusion

The celeste-radiant-yaml-command package has been found to contain malicious code, posing a serious threat to users. It is crucial to remove this package and monitor applications for any potential security breaches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for celeste-radiant-yaml-command →

Share this vulnerability

FAQ

It is an npm module for parsing and manipulating YAML files in applications.

The malicious code was identified by security researchers from Amazon Inspector.

Using this package can lead to unauthorized access, data breaches, and other security vulnerabilities.

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

Remove the package immediately and consider using a secure alternative. Monitor your application for any suspicious activity.

How To Fix

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

npm uninstall celeste-radiant-yaml-command

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