Malicious Code Detected in forge-vscode: A Critical Security Alert

forge-vscode Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20779: Malicious code in forge-vscode (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The forge-vscode package is a tool designed for developers using Visual Studio Code, providing functionalities to create and manage Forge applications. It is widely utilized in the development community for its ease of integration and robust features. However, recent findings have revealed that the package contains malicious code, posing significant security risks to users and their projects.

Vulnerability Detail

The vulnerability in the forge-vscode package originates from the introduction of malicious code that can compromise user systems. This code may lead to unauthorized access, data breaches, or the execution of harmful operations within the user's environment. The severity of this vulnerability is heightened by the package's popularity and the potential for widespread exploitation among developers.

How To Fix

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

npm uninstall forge-vscode

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 remove the forge-vscode package from their project until a secure version is confirmed. This can be done using the command: 'npm uninstall forge-vscode'. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the forge-vscode package highlights the importance of vigilance in software development. Users are urged to take immediate action by updating or removing the affected package to safeguard their projects and systems. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for forge-vscode →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to user systems, leading to data breaches and other harmful activities.

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

If an immediate update is not possible, consider uninstalling the package and using alternative solutions until a secure version is available.

Regularly check the package's repository and subscribe to vulnerability alert services like Vulert to receive real-time notifications.

It is not recommended to continue using forge-vscode until the vulnerability is addressed and a secure version is released.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall forge-vscode

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