Top issues
Detected presence of severe vulnerabilities with active exploitation.
Causes risk: actively exploited vulnerabilities
vulnerabilities
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
67 packages
found in
Top 100
548 packages
found in
Top 1k
3078 packages
found in
Top 10k
17.39k 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.
Detected presence of high severity vulnerabilities.
Causes risk: high severity vulnerabilities
vulnerabilities
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
68 packages
found in
Top 100
555 packages
found in
Top 1k
3086 packages
found in
Top 10k
17.47k 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
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 services 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 leverages 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.
Detected presence of medium severity vulnerabilities.
Causes risk: medium severity vulnerabilities
vulnerabilities
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 medium severity.Prevalence in Visual Studio Code community
64 packages
found in
Top 100
530 packages
found in
Top 1k
2998 packages
found in
Top 10k
16.52k 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 contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.Prevalence in Visual Studio Code community
60 packages
found in
Top 100
434 packages
found in
Top 1k
2301 packages
found in
Top 10k
13.88k packages
in community
Next steps
Investigate reported detections.
If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.
Top behaviors
Modifies file/directory permissions.
permissions
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
67 packages
found in
Top 100
547 packages
found in
Top 1k
2891 packages
found in
Top 10k
14.99k packages
in community
Might contain potentially obfuscated code or data.
anomaly
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
84 packages
found in
Top 100
679 packages
found in
Top 1k
4393 packages
found in
Top 10k
30.42k packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
82 packages
found in
Top 100
636 packages
found in
Top 1k
3971 packages
found in
Top 10k
25.82k packages
in community
Contains URLs that link to raw files on GitHub.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
79 packages
found in
Top 100
622 packages
found in
Top 1k
4233 packages
found in
Top 10k
29.36k packages
in community
Contains URLs that link to interesting file formats.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
59 packages
found in
Top 100
488 packages
found in
Top 1k
2687 packages
found in
Top 10k
15.88k packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(8 Active Vulnerabilities)
2 (2 Fixable)
CVE-2022-3517h
CVE-2025-64718m
6 (6 Fixable)
CVE-2021-23343h
CVE-2020-8203h
CVE-2021-23337h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated