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 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
60 packages
found in
Top 100
453 packages
found in
Top 1k
2271 packages
found in
Top 10k
12.07k 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 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
161 packages
found in
Top 1k
472 packages
found in
Top 10k
1.89k 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
12 packages
found in
Top 100
102 packages
found in
Top 1k
348 packages
found in
Top 10k
1.32k 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
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.
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
Contains potentially obfuscated code or data.
packer
Prevalence in Visual Studio Code community
Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
4 packages
found in
Top 100
27 packages
found in
Top 1k
70 packages
found in
Top 10k
398 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
Encrypts data using RSA with a given public key.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
25 packages
found in
Top 100
203 packages
found in
Top 1k
712 packages
found in
Top 10k
3.46k packages
in community
Encrypts data using RSA with a given private key.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
18 packages
found in
Top 100
120 packages
found in
Top 1k
506 packages
found in
Top 10k
2.56k packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(5 Active Vulnerabilities)
2 (1 Fixable)
CVE-2023-46233c
CVE-2025-57350h
3 (3 Fixable)
CVE-2024-21538h
CVE-2022-25883h
CVE-2022-31129h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated