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

aiocpa

Artifact:
latest
malicious
Research
sync & async Crypto Pay API client.
License: Permissive (MIT)
Published: about 1 year 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
3 malware-like behaviors found
Malware
4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
about 1 year agoReported By: ReversingLabs (Researcher)
Learn more about malware detection
malware
about 1 year agoReported By: Community (Phylum)
malware
about 1 year agoReported By: Community (Snyk)

Popularity

12.71k
Total Downloads
Contributor
Declared Dependencies
0
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 PyPI community

0 packages
found in
Top 100
0 packages
found in
Top 1k
5 packages
found in
Top 10k
13913 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 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

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 raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-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 code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.

Prevalence in PyPI community

33 packages
found in
Top 100
206 packages
found in
Top 1k
1631 packages
found in
Top 10k
63840 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 an alternative delivery mechanism for software packages.

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.

Top behaviors

Prevalence in PyPI community

Behavior often found in this community (Common)
40 packages
found in
Top 100
253 packages
found in
Top 1k
1433 packages
found in
Top 10k
53416 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
33 packages
found in
Top 100
207 packages
found in
Top 1k
1634 packages
found in
Top 10k
63910 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
23 packages
found in
Top 100
80 packages
found in
Top 1k
436 packages
found in
Top 10k
9770 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
54 packages
found in
Top 100
343 packages
found in
Top 1k
1872 packages
found in
Top 10k
49508 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
49 packages
found in
Top 100
364 packages
found in
Top 1k
2374 packages
found in
Top 10k
87567 packages
in community

Top vulnerabilities

No vulnerabilities found.