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
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 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.
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
70 packages
found in
Top 100
531 packages
found in
Top 1k
3115 packages
found in
Top 10k
16606 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 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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.Prevalence in Visual Studio Code community
57 packages
found in
Top 100
447 packages
found in
Top 1k
3421 packages
found in
Top 10k
56684 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.
Detected presence of low severity vulnerabilities.
Causes risk: low 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 low severity.Prevalence in Visual Studio Code community
55 packages
found in
Top 100
423 packages
found in
Top 1k
2177 packages
found in
Top 10k
11013 packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.
Top behaviors
Might contain potentially obfuscated code or data.
anomaly
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
85 packages
found in
Top 100
673 packages
found in
Top 1k
4329 packages
found in
Top 10k
28768 packages
in community
Opens URLs during installation or upon launch.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
47 packages
found in
Top 100
303 packages
found in
Top 1k
1634 packages
found in
Top 10k
8176 packages
in community
Executes files during installation or upon launch.
execution
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
94 packages
found in
Top 100
834 packages
found in
Top 1k
6690 packages
found in
Top 10k
83799 packages
in community
Creates a process.
execution
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
82 packages
found in
Top 100
646 packages
found in
Top 1k
3580 packages
found in
Top 10k
19750 packages
in community
Contains Korean Local credit card numbers.
steal
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
62 packages
found in
Top 100
474 packages
found in
Top 1k
2491 packages
found in
Top 10k
12771 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(4 Active Vulnerabilities)
2 (1 Fixable)
CVE-2022-3517h
CVE-2025-57352m
2 (2 Fixable)
CVE-2022-25883h
CVE-2025-5889l
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated