Top issues
Detected presence of malicious files through analyst-vetted file reputation.
Causes risk: analyst-vetted malware found
threats
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
1 packages
found in
Top 100
15 packages
found in
Top 1k
52 packages
found in
Top 10k
312 packages
in community
Next steps
Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
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
71 packages
found in
Top 100
568 packages
found in
Top 1k
3198 packages
found in
Top 10k
16595 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 critical severity vulnerabilities.
Causes risk: critical 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 critical severity.Prevalence in Visual Studio Code community
64 packages
found in
Top 100
445 packages
found in
Top 1k
2064 packages
found in
Top 10k
9214 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.
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
72 packages
found in
Top 100
583 packages
found in
Top 1k
3344 packages
found in
Top 10k
17282 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
78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 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.
Top behaviors
Retrieves the name of the user associated with the process.
search
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
21 packages
found in
Top 100
135 packages
found in
Top 1k
319 packages
found in
Top 10k
1413 packages
in community
Modifies file/directory permissions.
permissions
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community
Permits an incoming connection on a TCP socket.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
28 packages
found in
Top 100
169 packages
found in
Top 1k
418 packages
found in
Top 10k
1486 packages
in community
Opens a socket listening for an incoming connection.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
23 packages
found in
Top 100
139 packages
found in
Top 1k
333 packages
found in
Top 10k
1311 packages
in community
Deletes files in Windows system directories.
file
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
26 packages
found in
Top 100
152 packages
found in
Top 1k
335 packages
found in
Top 10k
1452 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(4 Active Vulnerabilities)
1 (1 Fixable)
CVE-2022-3517h
3 (3 Fixable)
CVE-2021-44906c
CVE-2020-7598m
CVE-2025-5889l
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated