Spectra Assure
Community
Docs
failIncident: Malware
Scanned: about 3 hours ago

GitLab Workflow

Artifact:
License: unknown
Published: 10 months ago

Publisher: GitLab


SAFE Assessment

Compliance

Licenses
4 software distribution restrictions
Secrets
2 debugging symbols found

Security

Vulnerabilities
56 severe vulnerabilities exploited
Hardening
3 baseline mitigations missing

Threats

Tampering
3 suspicious application behaviors
Malware
4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
8 months agoReported By: ReversingLabs (Automated)
Learn more about malware detection
malware
Reported By: ReversingLabs (Researcher)
Learn more about malware detection

Popularity

2.63M
Total Installs
Contributor
Declared Dependencies
1
Dependents

Top issues

Problem

Potentially unwanted applications (PUAs) can be considered a risk by some software users. This threat type typically collects private user data, or in more extreme cases, tampers with system security settings. Most threat prevention solutions detect and block PUAs. Software packages that trigger security solution detections also tend to increase the number of support calls and open tickets from users.

Prevalence in Visual Studio Code community

2 packages
found in
Top 100
2 packages
found in
Top 1k
2 packages
found in
Top 10k
47 packages
in community

Next steps

Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.

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

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. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.

Prevalence in Visual Studio Code community

27 packages
found in
Top 100
206 packages
found in
Top 1k
910 packages
found in
Top 10k
3803 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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
48 packages
found in
Top 100
323 packages
found in
Top 1k
1111 packages
found in
Top 10k
4964 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
42 packages
found in
Top 100
313 packages
found in
Top 1k
1548 packages
found in
Top 10k
7212 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
4 packages
found in
Top 100
19 packages
found in
Top 1k
68 packages
found in
Top 10k
215 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
3 packages
found in
Top 100
22 packages
found in
Top 1k
88 packages
found in
Top 10k
279 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(139 Active Vulnerabilities)
48 (46 Fixable)
CVE-2024-42461c
CVE-2024-48949c
CVE-2023-45133h
89 (85 Fixable)
CVE-2019-10746c
CVE-2019-10747c
CVE-2020-7774c
2 (2 Fixable)
CVE-2022-29078c
CVE-2022-24785h
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated