Our AI threat analyst detects malicious packages and blogs about OSS compromises
7000 write-ups and countingRead one

Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

VS Code

Search by package name, PURL or hash

passEverything is awesome!

Scanned:

LM Studio Code

Artifact:

latest

Top 10k

Agentic coding panel for your local LM Studio models. A Claude Code / Codex–style chat experience powered by the open-source OpenCode agent, running entirely against your local models.

License: Permissive (MIT)

Published:

Publisher: cgaspard

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Overview issues9 vulnerabilities0 malware0 behaviors183 dependencies1 contributors1 versions40

List of software quality issues with the number of affected components.

Policies

Info

Problem

Operating systems execute application code in multiple privilege access levels. Separation of privileges is designed to protect the stability and integrity of the operating system by shielding it from issues that the user run applications may cause. However, some users may need to interact with higher privilege parts of the operating system to accomplish specific tasks. For this purpose, operating systems provide facilities that users may leverage to temporarily elevate their running privileges. Users with higher privileges can run any application with the same privilege level as their own. Attackers often try to trick privileged users into running malicious code, enabling them to infect the operating system. While the presence of code that elevates user privileges does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that can elevate user privileges. One example of acceptable use for such functions is allowing the users to install software packages and updates.

Prevalence in Visual Studio Code community

33 packages

found in

Top 100

175 packages

found in

Top 1k

402 packages

found in

Top 10k

1.46k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1548 - Abuse Elevation Control Mechanism.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Software components are typically distributed in standardized packaging formats. Software packages are built from instructions written within package manifests that act as blueprints for package assembly. A package manifest declares the most important software properties, such as the package name, its authors and license, external dependencies, and various actions that may occur during the package lifecycle. Package managers are specialized tools used by developers to manage software components. Package managers read these manifests to deploy software components along with their dependencies. The premise of the package management system is that software components are isolated from each other, and that they rely on the package manager to provide their dependencies. However, it was detected that a software component includes code capable of accessing or modifying directories that are maintained exclusively by package managers. This is unusual as it resembles tactics used by threat actors that tamper with installed software components and inject malicious code into trusted execution paths.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Software components sometimes need to interact with sensitive parts of the runtime environment, often requiring privileged access to accomplish a task. Cloud workload configuration includes high-value information such as cloud provider credentials, environment variables containing secrets, and configuration files used by cloud and container orchestration tools. That information is used by applications running in cloud and containerized environments. Attackers often abuse access to cloud workload configuration to harvest secrets from developer machines and build environments, which can later be exfiltrated to attacker-controlled infrastructure and used to gain unauthorized access to cloud resources. While the presence of code that accesses cloud workload configuration does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select software components should consider using functions that read cloud workload configuration. One example of acceptable use for such functions is infrastructure-as-code tooling that legitimately needs to read credentials to provision or manage cloud resources on behalf of the developer.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1580 - Cloud Infrastructure Discovery.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing service URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverage the GitHub service to deliver malicious payloads.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

622 packages

found in

Top 1k

4233 packages

found in

Top 10k

29.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in Visual Studio Code community

25 packages

found in

Top 100

151 packages

found in

Top 1k

793 packages

found in

Top 10k

3.71k packages

in community

Next steps

Check the software component behaviors for anomalies.

Consider exploratory software component testing within a sandbox environment.

Consider replacing the software component with a more widely used alternative.

Avoid using this software package until it is vetted as safe.

Problem

Software components sometimes need to interact with higher privilege parts of the operating system, often requiring administrative access to accomplish a task. Operating systems include a complete network stack with many services that allow the machine to connect to the internet. Some of these services are used to secure network access. For that reason, attackers often aim to tamper with system network settings. Disabling firewalls and other network security features enable the malicious code to execute without being blocked. While the presence of code that tampers with system network settings does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that interact with system network settings. One example of acceptable use for such functions is allowing specialized applications to use non-standard network ports by updating the firewall allowlist.

Prevalence in Visual Studio Code community

16 packages

found in

Top 100

67 packages

found in

Top 1k

161 packages

found in

Top 10k

590 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1562.004 - Disable or Modify System Firewall.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. Top-level domains (TLD) are a part of the Domain Name System (DNS), and are used to lookup an Internet Protocol (IP) address of a requested website. There are a few different types of top-level domains. Generic, sponsored and country-code TLDs are generally accessible to the public. Registrars that govern the assignment of domain names within the TLD may choose to sell specific domain names to an interested party. However, some registrars are known to have less strict rules for assigning domain names. Attackers often abuse gaps in governance and actively seek to register their malicious domains in such TLDs. This issue is raised for all domains registered within TLDs that harbor an excessive number of malicious sites. While the presence of suspicious TLDs does not imply malicious intent, all of its uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

44 packages

found in

Top 100

321 packages

found in

Top 1k

1549 packages

found in

Top 10k

16.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider changing the top-level domain to avoid being flagged by security solutions.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

560 packages

found in

Top 1k

2912 packages

found in

Top 10k

17.75k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider changing the port to one that is standard for the networking protocol.

Problem

Operating systems allow multiple user accounts to coexist on a single computer system. Each registered user has identity information associated with their account. At the very least, user accounts consist of a user name and an optional password. In some cases, user account data may also include personally identifiable information. Extended personal information may include user's given and last name, their email and mailing address, personal photo and their telephone number. Financially motivated attackers may seek to collect personal information for purposes of selling the private data to a third-party. Malicious code that typically exhibits these behavior traits is commonly referred to as an information stealer. While the presence of code that accesses identity information does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Accessing identity information is a very common behavior for software packages. One example of acceptable use for such functions is verifying that the active user has purchased a software license that allows them to run the application.

Prevalence in Visual Studio Code community

65 packages

found in

Top 100

419 packages

found in

Top 1k

1961 packages

found in

Top 10k

9.65k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

List of software quality issues with the number of affected components.

Policies

Info

Problem

Prevalence in Visual Studio Code community

33 packages

found in

Top 100

175 packages

found in

Top 1k

402 packages

found in

Top 10k

1.46k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1548 - Abuse Elevation Control Mechanism.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1580 - Cloud Infrastructure Discovery.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

622 packages

found in

Top 1k

4233 packages

found in

Top 10k

29.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

Problem

Prevalence in Visual Studio Code community

25 packages

found in

Top 100

151 packages

found in

Top 1k

793 packages

found in

Top 10k

3.71k packages

in community

Next steps

Check the software component behaviors for anomalies.

Consider exploratory software component testing within a sandbox environment.

Consider replacing the software component with a more widely used alternative.

Avoid using this software package until it is vetted as safe.

Problem

Prevalence in Visual Studio Code community

16 packages

found in

Top 100

67 packages

found in

Top 1k

161 packages

found in

Top 10k

590 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1562.004 - Disable or Modify System Firewall.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. Top-level domains (TLD) are a part of the Domain Name System (DNS), and are used to lookup an Internet Protocol (IP) address of a requested website. There are a few different types of top-level domains. Generic, sponsored and country-code TLDs are generally accessible to the public. Registrars that govern the assignment of domain names within the TLD may choose to sell specific domain names to an interested party. However, some registrars are known to have less strict rules for assigning domain names. Attackers often abuse gaps in governance and actively seek to register their malicious domains in such TLDs. This issue is raised for all domains registered within TLDs that harbor an excessive number of malicious sites. While the presence of suspicious TLDs does not imply malicious intent, all of its uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

44 packages

found in

Top 100

321 packages

found in

Top 1k

1549 packages

found in

Top 10k

16.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider changing the top-level domain to avoid being flagged by security solutions.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

560 packages

found in

Top 1k

2912 packages

found in

Top 10k

17.75k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider changing the port to one that is standard for the networking protocol.

Problem

Prevalence in Visual Studio Code community

65 packages

found in

Top 100

419 packages

found in

Top 1k

1961 packages

found in

Top 10k

9.65k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

LM Studio Code

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 37 malicious incidents in versions published within 2 years prior to the latestLatest version with malware incident detected: 25 days agoVersion: 0.30.1

INCIDENTS FOR THIS VERSION:

TH16120Detected presence of software components that can elevate the user privileges.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16129Detected presence of software components that can tamper with other installed software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16130Detected presence of software components that can access sensitive cloud workload configuration.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16113Detected presence of software components that can tamper with the system network settings.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17118Detected presence of files containing URLs that use suspicious top-level domains.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16126Detected presence of software components that can access user identity information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Did you know...

TH16120Detected presence of software components that can elevate the user privileges.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16129Detected presence of software components that can tamper with other installed software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16130Detected presence of software components that can access sensitive cloud workload configuration.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16113Detected presence of software components that can tamper with the system network settings.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17118Detected presence of files containing URLs that use suspicious top-level domains.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16126Detected presence of software components that can access user identity information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps