Spectra Assure
Community
failIncident: Removal
Scanned: 13 days ago

typescript

Artifact:
License: unknown
Published: almost 6 years ago

Publisher: Aish


SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
1 components prone to hijacking
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

removal
almost 4 years agoReported By: Community

Popularity

17.05k
Total Installs
Contributor
Declared Dependencies
0
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

Applications communicate with web services by exchanging HTTP requests. During software development, externally hosted services are used by developers to debug software quality issues relating to exchanging HTTP requests. Attackers commonly abuse tools designed for HTTP request inspection to monitor network traffic and extract sensitive information from the HTTP traffic. While the presence of domains related to HTTP inspection does not imply malicious intent, all of their uses in a software package should be documented and approved. Attackers might have purposely injected security testing tools in the software package to monitor the network traffic of the infected computer system. It is also possible that the software package has mistakenly included a part of its testing infrastructure during packaging.

Prevalence in Visual Studio Code community

32 packages
found in
Top 100
236 packages
found in
Top 1k
1220 packages
found in
Top 10k
7.61k 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 removing all references to flagged network locations.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.

Prevalence in Visual Studio Code community

1 packages
found in
Top 100
42 packages
found in
Top 1k
375 packages
found in
Top 10k
34.8k 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 that their versions are pinned.
Avoid using this software package until it is vetted as safe.

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 medium severity.

Prevalence in Visual Studio Code community

64 packages
found in
Top 100
530 packages
found in
Top 1k
2998 packages
found in
Top 10k
16.52k 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 Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
837 packages
found in
Top 1k
6746 packages
found in
Top 10k
87.76k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
69 packages
found in
Top 100
489 packages
found in
Top 1k
2679 packages
found in
Top 10k
15.3k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
70 packages
found in
Top 100
500 packages
found in
Top 1k
2940 packages
found in
Top 10k
18.75k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
54 packages
found in
Top 100
333 packages
found in
Top 1k
1926 packages
found in
Top 10k
12.1k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
88 packages
found in
Top 100
718 packages
found in
Top 1k
4377 packages
found in
Top 10k
28.84k packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(3 Active Vulnerabilities)
1 (1 Fixable)
CVE-2020-15168m
2 (2 Fixable)
CVE-2025-7783c
CVE-2022-0235m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated