Spectra Assure
Community
failIncident: Malware
Scanned: 14 days ago

librex

Ruby Exploitation Library (deprecated gem)
License: unknown
Published: over 11 years 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
2 malicious components found

INCIDENTS FOR THIS VERSION:

malware
over 1 year agoReported By: ReversingLabs (Automated)
Learn more about malware detection

Popularity

1.6M
Total Downloads
Contributors
Declared Dependencies
5
Dependents

Top issues

Problem

Third-party malware detection algorithms have determined that the software package contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered accurate, and can typically identify the malware family by name.

Prevalence in RubyGems community

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

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

50 packages
found in
Top 100
459 packages
found in
Top 1k
1913 packages
found in
Top 10k
23.3k packages
in community

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

Behavior often found in this community (Common)
16 packages
found in
Top 100
64 packages
found in
Top 1k
560 packages
found in
Top 10k
8.56k packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
8 packages
found in
Top 100
27 packages
found in
Top 1k
273 packages
found in
Top 10k
5.44k packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
6 packages
found in
Top 100
29 packages
found in
Top 1k
210 packages
found in
Top 10k
5.63k packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
7 packages
found in
Top 100
16 packages
found in
Top 1k
135 packages
found in
Top 10k
2.58k packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
1 packages
found in
Top 100
5 packages
found in
Top 1k
25 packages
found in
Top 10k
170 packages
in community

Top vulnerabilities

No vulnerabilities found.