Malicious Code Detected in @ra-ide/tag-editor-frontend: Version 141.3.1 Vulnerability

@ra-ide/tag-editor-frontend Updated 21 Nov 2025

Summary

20/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190597: Malicious code in @ra-ide/tag-editor-frontend (npm). Affects @ra-ide/tag-editor-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 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 package @ra-ide/tag-editor-frontend is a JavaScript library available through npm, designed for managing and editing tags in web applications. It provides developers with a user-friendly interface to implement tagging functionalities. However, version 141.3.1 of this package has been flagged for malicious behavior, specifically for communicating with a domain linked to harmful activities, raising significant security concerns for users and applications relying on it.

Vulnerability Detail

The vulnerability in @ra-ide/tag-editor-frontend arises from its communication with a domain associated with malicious activities. This could potentially lead to data breaches, unauthorized access, or the execution of harmful code within applications that utilize this package. The origin of this vulnerability has been identified by the OpenSSF Package Analysis project, which has classified the package as malicious due to its behavior. Users of this package should be aware of the risks involved and take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall @ra-ide/tag-editor-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

As a temporary workaround, you can remove the @ra-ide/tag-editor-frontend package from your project until a secure version is confirmed. You can do this by executing:

npm uninstall @ra-ide/tag-editor-frontend

This will help prevent any potential exploitation of the vulnerability while you seek a safer alternative.

Conclusion

The @ra-ide/tag-editor-frontend package version 141.3.1 has been identified as malicious, posing significant security risks to applications that utilize it. Users are urged to update to a patched version or remove the package until a secure alternative is available. Staying informed and proactive is crucial in maintaining the security of your applications.

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

Share this vulnerability

FAQ

The package communicates with a domain that is known for malicious activities, which poses a risk to applications using it.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By simply using your package-lock.json file, Vulert can help you identify if your application is impacted.

Yes, you can mitigate risks by updating the package to a secure version or removing it from your project until a safe version is available.

If immediate updates are not possible, consider removing the package as a temporary measure to avoid potential security risks.

Detailed information about this vulnerability can be found on the OpenSSF Package Analysis project page and through the Vulert platform.

How To Fix

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

npm uninstall @ra-ide/tag-editor-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