Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 5 days ago

ETHcode

Artifact:
latest
Ethereum IDE for VS Code
License: Permissive (MIT)
Published: 6 months ago

Publisher: 7finney



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
2 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
1 suspicious application behaviors
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

6.57k
Total Installs
Contributor
Declared Dependencies
2
Dependents

Top issues

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.

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.

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

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. Node Package Manager (NPM) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious NPM packages in their software projects. Most malicious packages published on NPM target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of NodeJS malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. The detection is strongly influenced by behaviors that software components exhibit. Behaviors similar to previously discovered malware and software supply chain attacks may cause some otherwise benign software packages to be detected by this policy.

Prevalence in Visual Studio Code community

10 packages
found in
Top 100
69 packages
found in
Top 1k
311 packages
found in
Top 10k
1.86k 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.

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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
14 packages
found in
Top 100
113 packages
found in
Top 1k
423 packages
found in
Top 10k
2.58k packages
in community

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

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
34 packages
found in
Top 100
237 packages
found in
Top 1k
903 packages
found in
Top 10k
4.31k packages
in community

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

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
40 packages
found in
Top 100
282 packages
found in
Top 1k
1349 packages
found in
Top 10k
7.08k packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
None
2 (2 Fixable)
CVE-2025-7783c
CVE-2025-58754h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated