Malicious Code Detected in @ra-ide/st-frontend Package - Version 141.3.1

@ra-ide/st-frontend Updated 21 Nov 2025

Summary

20/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190595: Malicious code in @ra-ide/st-frontend (npm). Affects @ra-ide/st-frontend versions 141.3.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @ra-ide/st-frontend package is a JavaScript library used in web development, primarily for frontend applications. It is designed to facilitate various functionalities within the npm ecosystem. However, this package has been flagged for malicious behavior, specifically for communicating with a domain associated with malicious activities, raising significant security concerns for developers and users relying on it.

Vulnerability Detail

The vulnerability in the @ra-ide/st-frontend package arises from its version 141.3.1, which has been identified as malicious by the OpenSSF Package Analysis project. The package's malicious nature is attributed to its communication with a domain linked to harmful activities. This can lead to potential data breaches, unauthorized access, and exploitation of systems that utilize this package, posing a serious risk to application integrity and user data security.

How To Fix

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

npm uninstall @ra-ide/st-frontend

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

If an immediate update is not feasible, consider removing the @ra-ide/st-frontend package from your project until a secure version is available. You can do this by running the command: npm uninstall @ra-ide/st-frontend. This will prevent any potential exploitation from the malicious code.

Conclusion

The @ra-ide/st-frontend package has been identified as malicious due to its communication with harmful domains. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can enhance vulnerability monitoring and ensure application security.

See every vulnerability recorded for @ra-ide/st-frontend →

Share this vulnerability

FAQ

The package communicates with a domain associated with malicious activities, which can compromise application security.

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

As a temporary measure, you can uninstall the @ra-ide/st-frontend package to mitigate the risk until a secure version is available.

Currently, the recommended action is to update to the latest version of the package that does not contain the malicious code.

Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights.

How To Fix

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

npm uninstall @ra-ide/st-frontend

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