Spectra Assure
Community
failIncident: Removal
Scanned: 1 day ago

CfxLua Code (FiveM/RedM IntelliSense)

Artifact:
latest
removed
IntelliSense support for the Lua Script runtime used by FiveM and RedM
License: Permissive (MIT)
Published: over 2 years ago

Publisher: heyyczer



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

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

INCIDENTS FOR THIS VERSION:

removal
almost 2 years agoReported By: Community

Popularity

7.33k
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

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 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. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in Visual Studio Code community

25 packages
found in
Top 100
151 packages
found in
Top 1k
793 packages
found in
Top 10k
3.71k packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

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. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in Visual Studio Code community

60 packages
found in
Top 100
434 packages
found in
Top 1k
2301 packages
found in
Top 10k
13.88k 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 the file attachments hosted on Discord. Attackers often abuse popular web services to host malicious payloads. Since file-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 Discord file-sharing locations does not imply malicious intent, no software should be directly linking to a Discord file attachment. An increasing number of software supply chain attacks in the open source space leverages the Discord file-sharing service to deliver malicious payloads.

Prevalence in Visual Studio Code community

0 packages
found in
Top 100
2 packages
found in
Top 1k
12 packages
found in
Top 10k
102 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.
Remove all references to flagged network locations.

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. Paste-and-share services are websites that allow their users to easily share code snippets and simple plain text documents. Users typically do not need to be registered on the website to publish and access shared information. For this reason, paste-and-share services are commonly used by malicious actors to deliver stages of their malware payloads. Many software supply chain attacks in the open source space leverage paste-and-share services to deliver malicious payloads. Presence of paste-and-share service references does not imply malicious intent. Software developers commonly include links to such services as documentation for various issues they encounter while writing and maintaining code bases.

Prevalence in Visual Studio Code community

14 packages
found in
Top 100
110 packages
found in
Top 1k
719 packages
found in
Top 10k
3.69k 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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
2 packages
found in
Top 1k
12 packages
found in
Top 10k
102 packages
in community

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)
88 packages
found in
Top 100
718 packages
found in
Top 1k
4377 packages
found in
Top 10k
28.84k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
79 packages
found in
Top 100
549 packages
found in
Top 1k
2932 packages
found in
Top 10k
14.71k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
78 packages
found in
Top 100
626 packages
found in
Top 1k
3730 packages
found in
Top 10k
24.28k packages
in community

Top vulnerabilities

No vulnerabilities found.