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

Code LLDB

Artifact:
latest
removed
malicious
Top 10k
A native debugger powered by LLDB. Debug C++, Rust and other compiled languages with VSCode
License: Permissive (MIT)
Published: 20 days ago
Publisher: codevsce
Visit Github
See on Visual Studio Code

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
2 analyst-vetted malware found

INCIDENTS FOR THIS VERSION:

malware
16 days agoReported By: Community (Secure Annex)
More info
removal
13 days agoReported By: Community
malware
11 days agoReported By: ReversingLabs (Researcher)
Learn more about malware detection

Popularity

15.41k
Total Installs
1
Contributor
3
Declared Dependencies
0
Dependents

Top issues

See all issues

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

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

4 packages
found in
Top 100
52 packages
found in
Top 1k
264 packages
found in
Top 10k
26547 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

0 packages
found in
Top 100
4 packages
found in
Top 1k
44 packages
found in
Top 10k
7143 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.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
81 packages
found in
Top 100
631 packages
found in
Top 1k
3887 packages
found in
Top 10k
24357 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
73 packages
found in
Top 100
573 packages
found in
Top 1k
3170 packages
found in
Top 10k
17492 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
83 packages
found in
Top 100
638 packages
found in
Top 1k
3956 packages
found in
Top 10k
23785 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
70 packages
found in
Top 100
529 packages
found in
Top 1k
2780 packages
found in
Top 10k
13531 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
834 packages
found in
Top 1k
6690 packages
found in
Top 10k
83799 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for Code LLDB

What is Code LLDB?

A native debugger powered by LLDB. Debug C++, Rust and other compiled languages with VSCode. For more information about this package, visit its homepage.

Is Code LLDB malicious or is it safe to use?

The VS Code package Code LLDB has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. 1 other issue and risky behavior was found. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the Code LLDB package were malicious.

Is Code LLDB popular?

The VS Code package Code LLDB ranks among the top 10000 projects in this community. It has 15K recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure Code LLDB once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Code LLDB behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Code LLDB version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.