Spectra Assure
Community
failIncident: Malware
Scanned: 3 days ago

@yoobic/design-system

YOOBIC Stencil common items
License: unknown
Published: 4 months ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
7 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
1 suspicious application behaviors
Malware
4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
4 months agoReported By: Community (Socket)
malware
4 months agoReported By: Community (StepSecurity)
malware
4 months agoReported By: Community (Semgrep)
malware
4 months agoReported By: Community (Aikido)
malware
4 months agoReported By: ReversingLabs (Researcher)
See more info on our blog
malware
4 months agoReported By: Community (Wiz)
malware
4 months agoReported By: Community (GitHub Advisory)
malware
4 months agoReported By: Community (Sonatype)
malware
4 months agoReported By: Community (OpenSSF)
removal
N/AReported By: Community

Popularity

221.3k
Recorded Downloads Since 2021
Contributors
Declared Dependencies
3
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 npm community

9 packages
found in
Top 100
9 packages
found in
Top 1k
37 packages
found in
Top 10k
19.1k 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 npm community

9 packages
found in
Top 100
7 packages
found in
Top 1k
26 packages
found in
Top 10k
19.19k packages
in community

Next steps

Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.

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 npm community

24 packages
found in
Top 100
101 packages
found in
Top 1k
1359 packages
found in
Top 10k
511.03k 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 npm community

7 packages
found in
Top 100
50 packages
found in
Top 1k
843 packages
found in
Top 10k
309.68k 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 npm community

22 packages
found in
Top 100
114 packages
found in
Top 1k
1440 packages
found in
Top 10k
528.88k 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

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
19 packages
found in
Top 10k
2.71k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
21 packages
found in
Top 10k
2.85k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
18 packages
found in
Top 10k
2.86k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
22 packages
found in
Top 100
136 packages
found in
Top 1k
1267 packages
found in
Top 10k
411.22k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
15 packages
found in
Top 10k
2.32k packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(18 Active Vulnerabilities)
5 (5 Fixable)
CVE-2020-15256c
CVE-2021-30109m
CVE-2024-51434m
13 (13 Fixable)
CVE-2021-23370c
CVE-2021-23434h
CVE-2020-28478h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated