erc20-approve-audit
Affected
- Versions:
0.9.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in erc20-approve-audit (RubyGems)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (e43c1d294111db5834d006f064d33001b463860783ed8662a5f41a8e7354e4b8)
The gem's native extension script, which runs automatically during gem install, base64-decodes a Ruby payload and launches it via a double-forked, detached, session-leader background process (setsid, /dev/null reopen, ~20-40 minute delay). The decoded payload opens a TCP socket to the hardcoded bare IP 45.138.12.177:8089 and pipes a local /bin/sh to the socket in an infinite reconnect loop, giving a remote operator full shell control of the installer's host. Execution is gated by anti-analysis checks that suppress the payload inside CI providers (CI, GITHUB_ACTIONS, TRAVIS, JENKINS, GITLAB_CI, CODESPACES), ephemeral/sandbox hosts (uvm, firecracker, sandbox, vagrant), analyst-shaped usernames and working directories (/tmp, /var/tmp, /opt/rubygems, /workspace), and short machine uptimes (<1800s), firing only when developer-signal files are present (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.bundle, ~/.npmrc). The gem's advertised identity does not match its shipped contents: the name is erc20-approve-audit but the README and the native makefile target are bitcoin-rpc-lite / bitcoin_rpc_lite_native, and the Ruby library surface is a two-method stub (build_id='ok', healthy?=true) with no functional code.
Source: ossf-package-analysis (72bf8663ed3f4b92a50b3f9988ce63092fe827b55a65c726eee1f8f61163d890)
The OpenSSF Package Analysis project identified 'erc20-approve-audit' @ 0.9.1 (rubygems) as malicious.
It is considered malicious because:
Not rated by the source.
0.9.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0