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 Windows executable files with imported functions susceptible to pointer hijacking.
Causes risk: execution hijacking concerns
hardening
Problem
Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Imported function addresses are pointers to the symbols that implement the application-required functionality. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.Prevalence in Visual Studio Code community
20 packages
found in
Top 100
156 packages
found in
Top 1k
474 packages
found in
Top 10k
1793 packages
in community
Next steps
Review the programming language linker options, and consider a build toolchain update.
Detected Windows executable files with TLS callbacks susceptible to pointer hijacking.
Causes risk: execution hijacking concerns
hardening
Problem
Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Thread local storage (TLS) callbacks are pointers to code initialization and resource release functions. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.Prevalence in Visual Studio Code community
13 packages
found in
Top 100
101 packages
found in
Top 1k
347 packages
found in
Top 10k
1272 packages
in community
Next steps
Review the programming language linker options, and consider a build toolchain update.
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
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
29 packages
found in
Top 100
169 packages
found in
Top 1k
380 packages
found in
Top 10k
1338 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.
Top behaviors
Sends data on a connected TCP socket.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
73 packages
found in
Top 100
570 packages
found in
Top 1k
2843 packages
found in
Top 10k
14439 packages
in community
Receives data from a connected TCP socket.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
70 packages
found in
Top 100
538 packages
found in
Top 1k
2415 packages
found in
Top 10k
11250 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
(10 Active Vulnerabilities)
7 (7 Fixable)
CVE-2025-58764h
CVE-2025-59041h
CVE-2025-59536h
3 (3 Fixable)
CVE-2025-52882h
CVE-2025-54795h
CVE-2025-64755h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated