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

lbank-connector-pythons

Artifact:
latest
malicious
Research
LBANK connector for the public API, private API, and websockets.
License: Permissive (MIT)
Published: 13 days ago


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
2 malware-like behaviors found
Malware
5 analyst-vetted malware found

INCIDENTS:

malware
8 days agoReported By: ReversingLabs (Researcher)
Learn more about malware detection

Popularity

303
Total Downloads
Contributors
Declared Dependencies
0
Dependents

Top 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 PyPI community

0 packages
found in
Top 100
0 packages
found in
Top 1k
7 packages
found in
Top 10k
13959 packages
in community

Next steps

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

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 exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the infostealer malware profile. Infostealers are commonly used to steal sensitive user data such as stored login details, financial information, and other personally identifiable information.

Prevalence in PyPI community

0 packages
found in
Top 100
0 packages
found in
Top 1k
1 packages
found in
Top 10k
1960 packages
in community

Next steps

Investigate reported detections.
Investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed.
In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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. Python Package Index (PyPI) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious PyPI packages in their software projects. Most malicious packages published on PyPI target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of Python malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. The detection is strongly influenced by behaviors that software components exhibit. Behaviors similar to previously discovered malware and software supply chain attacks may cause some otherwise benign software packages to be detected by this policy.

Prevalence in PyPI community

47 packages
found in
Top 100
226 packages
found in
Top 1k
1735 packages
found in
Top 10k
74797 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

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. Some open source repositories allow the developers to take down software component versions that they have published. For open source projects, version unpublishing is uncommon. Versions are typically removed due to a security incident, such as malicious code tampering or accidental development secrets exposure. Software developers often prioritize taking down such packages before informing the community that they have experienced a security incident. Therefore, it is prudent to review the reasons behind software version removals as these events might be a signal of an ongoing software supply chain attack.

Prevalence in PyPI community

No prevalence information at this time

Next steps

Review software component documentation for the reasons behind the recent version removal.
If the software version was removed due to a security incident, 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 PyPI community

No prevalence information at this time

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

Prevalence in PyPI community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
6 packages
found in
Top 1k
303 packages
found in
Top 10k
8293 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
39 packages
found in
Top 100
280 packages
found in
Top 1k
1754 packages
found in
Top 10k
67026 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
68 packages
found in
Top 100
508 packages
found in
Top 1k
3570 packages
found in
Top 10k
165477 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
26 packages
found in
Top 100
157 packages
found in
Top 1k
1202 packages
found in
Top 10k
28931 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
2 packages
found in
Top 100
14 packages
found in
Top 1k
96 packages
found in
Top 10k
2834 packages
in community

Top vulnerabilities

No vulnerabilities found.