List of software quality issues with the number of affected components.
category ALL
Policies
Info
Category
Problem
Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.
Prevalence in Visual Studio Code community
1 packages
found in
Top 100
6 packages
found in
Top 1k
7 packages
found in
Top 10k
360 packages
in community
Next steps
If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
Problem
Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.
Prevalence in Visual Studio Code community
0 packages
found in
Top 100
5 packages
found in
Top 1k
5 packages
found in
Top 10k
380 packages
in community
Next steps
Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
Problem
Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.
Prevalence in Visual Studio Code community
77 packages
found in
Top 100
613 packages
found in
Top 1k
3684 packages
found in
Top 10k
27.66k packages
in community
Next steps
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as critical severity.
Prevalence in Visual Studio Code community
67 packages
found in
Top 100
514 packages
found in
Top 1k
2838 packages
found in
Top 10k
19.06k packages
in community
Next steps
Perform impact analysis for the reported CVEs.
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Problem
Development extensions are commonly used by software developers to extend the functionality of integrated development environments, code editors, and other developer tools. Extensions are typically distributed through public marketplaces as packages that bundle the extension code with supporting resources. Development extension code implements behaviors that integrate it with the host application. This integration allows extensions to register commands, react to editor events, or provide programming language support. Extension code is loaded and executed automatically by the host application during events such as editor startup, file opening, or user interaction. These events are used by extension developers to set up the environment for nominal extension use, or to respond to activity within the host application. However, extensions are commonly abused by threat actors to execute arbitrary commands within the development environment. It was detected that the extension code could execute commands that are not typically used by development tools. Such unusual commands resemble common threat actor tactics and are usually obscured by layers of cryptography, code obfuscation, anti-analysis features, and other detection evasion techniques.
Prevalence in Visual Studio Code community
3 packages
found in
Top 100
5 packages
found in
Top 1k
138 packages
found in
Top 10k
768 packages
in community
Next steps
Investigate reported detections.
Consult Mitre ATT&CK documentation: T1176.002 - Software Extensions: IDE Extensions.
If the development extension intent does not relate to the reported behavior, investigate your development environment for software supply chain compromise.
You should stop using the development extension until the investigation is completed, or until the issue is risk accepted.
Consider replacing the development extension with an alternative.
Problem
Development extensions are commonly used by software developers to extend the functionality of integrated development environments, code editors, and other developer tools. Extensions are typically distributed through public marketplaces as packages that bundle the extension code with supporting resources. Development extension code implements behaviors that integrate it with the host application. This integration allows extensions to register commands, react to editor events, or provide programming language support. Extension code is loaded and executed automatically by the host application during events such as editor startup, file opening, or user interaction. These events are used by extension developers to set up the environment for nominal extension use, or to respond to activity within the host application. It is unusual for certain types of development extensions to invoke commands that download additional content from a remote server. Attackers commonly abuse development extensions to fetch malicious payloads from public code repositories, file sharing websites, or their own infrastructure. Remotely hosted content is not immutable, allowing the attackers to change the type of malware they deploy at any time.
Prevalence in Visual Studio Code community
3 packages
found in
Top 100
10 packages
found in
Top 1k
192 packages
found in
Top 10k
1.11k packages
in community
Next steps
Investigate reported detections.
Consult Mitre ATT&CK documentation: T1176.002 - Software Extensions: IDE Extensions.
If the development extension intent does not relate to the reported behavior, investigate your development environment for software supply chain compromise.
You should stop using the development extension until the investigation is completed, or until the issue is risk accepted.
Consider replacing the development extension with an alternative.
Problem
Development extensions are commonly used by software developers to extend the functionality of integrated development environments, code editors, and other developer tools. Extensions are typically distributed through public marketplaces as packages that bundle the extension code with supporting resources. Development extension code implements behaviors that integrate it with the host application. This integration allows extensions to register commands, react to editor events, or provide programming language support. Extension code is loaded and executed automatically by the host application during events such as editor startup, file opening, or user interaction. These events are used by extension developers to set up the environment for nominal extension use, or to respond to activity within the host application. It is unusual for certain types of development extensions to execute commands that can collect sensitive system information. Attackers often abuse development extensions to run commands that collect identifiable system information such as hostnames, user names, folder structures, and other data points that could help them understand the environment in which their malicious code was loaded.
Prevalence in Visual Studio Code community
3 packages
found in
Top 100
8 packages
found in
Top 1k
161 packages
found in
Top 10k
905 packages
in community
Next steps
Investigate reported detections.
Consult Mitre ATT&CK documentation: T1176.002 - Software Extensions: IDE Extensions.
If the development extension intent does not relate to the reported behavior, investigate your development environment for software supply chain compromise.
You should stop using the development extension until the investigation is completed, or until the issue is risk accepted.
Consider replacing the development extension with an alternative.
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. The ReversingLabs community package index may place software packages into quarantine during an ongoing security incident investigation. When a software project is placed into quarantine, it is typically unavailable for installation. Additionally, repository maintainers may also hide quarantined software projects from users that might stumble upon them using repository search functions. Quarantine is typically raised for software projects that were reported for unusual code changes or unexpected software behaviors.
Prevalence in Visual Studio Code community
10 packages
found in
Top 100
100 packages
found in
Top 1k
542 packages
found in
Top 10k
2.77k packages
in community
Next steps
Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.
Avoid using this software package until it is vetted as safe.
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.
Prevalence in Visual Studio Code community
77 packages
found in
Top 100
623 packages
found in
Top 1k
3795 packages
found in
Top 10k
29.26k packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
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
79 packages
found in
Top 100
540 packages
found in
Top 1k
3333 packages
found in
Top 10k
24.83k packages
in community
Next steps
Investigate reported detections as indicators of software tampering.