Spectra Assure
Community
Docs
failIncident: Malware
Scanned: 4 days ago

ETHcode

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

Publisher: 7finney



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
4 severe vulnerabilities exploited
Hardening
2 execution hijacking concerns

Threats

Tampering
1 suspicious application behaviors
Malware
3 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
5 months agoReported By: ReversingLabs (Researcher)
Learn more about malware detection
malware
5 months agoReported By: ReversingLabs (Automated)
Learn more about malware detection
removal
Reported By: Community

Popularity

6.47k
Total Installs
Contributor
Declared Dependencies
2
Dependents

Top issues

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.

Prevalence in Visual Studio Code community

2 packages
found in
Top 100
16 packages
found in
Top 1k
55 packages
found in
Top 10k
301 packages
in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.
Avoid using this software package.

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.

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package has one or more malicious dependencies. Some software dependencies may be optional, and could be installed or downloaded only if a certain pre-defined condition is met. When software dependencies are confirmed to be found within the software package, additional issues might also be reported. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks.

Prevalence in Visual Studio Code community

5 packages
found in
Top 100
48 packages
found in
Top 1k
192 packages
found in
Top 10k
638 packages
in community

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.
Avoid using this software package until it is vetted as safe.

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.

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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
3 packages
found in
Top 100
26 packages
found in
Top 1k
64 packages
found in
Top 10k
359 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
15 packages
found in
Top 100
110 packages
found in
Top 1k
397 packages
found in
Top 10k
2369 packages
in community

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

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
24 packages
found in
Top 100
194 packages
found in
Top 1k
687 packages
found in
Top 10k
3206 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
18 packages
found in
Top 100
119 packages
found in
Top 1k
500 packages
found in
Top 10k
2416 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(13 Active Vulnerabilities)
6 (6 Fixable)
CVE-2024-42461c
CVE-2024-48949c
CVE-2025-6545c
7 (7 Fixable)
CVE-2025-7783c
CVE-2025-9287c
CVE-2025-9288c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated