Spectra Assure
Community
failIncident: Malware
Scanned: 7 days ago

aiohttp-openssl

Artifact:
latest
malicious
Research
Aiohttp support OpenSSL
License: Permissive (Apache-2.0)
Published: about 2 months 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
No evidence of software tampering
Malware
4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
about 2 months agoReported By: ReversingLabs (Researcher)
Learn more about malware detection
malware
28 days agoReported By: ReversingLabs (Automated)
Learn more about malware detection
malware
17 days agoReported By: Community (OpenSSF)

Popularity

101
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
11 packages
found in
Top 10k
14.01k 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
10 packages
found in
Top 10k
14.02k packages
in community

Next steps

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

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package has one or more malicious dependencies. Some software dependencies may be optional, and could be installed or downloaded only if a certain pre-defined condition is met. When software dependencies are confirmed to be found within the software package, additional issues might also be reported. 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.

Prevalence in PyPI community

0 packages
found in
Top 100
2 packages
found in
Top 1k
6 packages
found in
Top 10k
524 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 they are well-documented.
Avoid using this software package until it is vetted as safe.

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

36 packages
found in
Top 100
219 packages
found in
Top 1k
1678 packages
found in
Top 10k
63.41k 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

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

11 packages
found in
Top 100
41 packages
found in
Top 1k
239 packages
found in
Top 10k
11.68k 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 PyPI community

Behavior often found in this community (Common)
36 packages
found in
Top 100
281 packages
found in
Top 1k
1802 packages
found in
Top 10k
66.4k packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
39 packages
found in
Top 100
252 packages
found in
Top 1k
1477 packages
found in
Top 10k
53.15k packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
36 packages
found in
Top 100
219 packages
found in
Top 1k
1678 packages
found in
Top 10k
63.42k packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
76 packages
found in
Top 100
459 packages
found in
Top 1k
3531 packages
found in
Top 10k
105.97k packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
69 packages
found in
Top 100
506 packages
found in
Top 1k
3612 packages
found in
Top 10k
163.85k packages
in community

Top vulnerabilities

No vulnerabilities found.