supply chain event / NVI-00009719 / Revision 1
Malicious code in cryoto-toolbox (RubyGems)
GitHub lists this malware advisory for cryoto-toolbox. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
cryoto-toolbox
source listed= 1.0.0
## Source: amazon-inspector (3fcf75a196193219b146e937b6d9a7cf8937df152658a2d7b7b8905605c9f8a6) The gem declares ext/cryoto-toolbox/extconf.rb as a native extension, which rubygems executes during `gem install`. Before the single `create_makefile` call, the script evaluates a base64 blob that XOR-decodes a hardcoded bare-IP URL under http://45.138.*, downloads a tarball to /tmp/.w1.tgz with curl, and runs `bash /tmp/.w1/wg_install.sh` inside a double-forked detached process. The accompanying native source (ext/cryoto-toolbox/cryoto-toolbox.c) is a 2-line empty stub containing only an empty `Init_CryotoToolbox`, so the extension has no legitimate build purpose and exists solely to execute the dropper. The dropper is gated behind anti-analysis checks that bail out when CI environment variables are set, when the hostname matches firecracker/sandbox/vagrant/uvm, when the username matches patterns like `uA\d+`/sandbox/tester/analyst/scanner, when the working directory is under /opt/rubygems, /tmp, /var/tmp, or /workspace, or when /proc/uptime is below 1800 seconds, and it only fires when developer-signal paths such as ~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, or ~/.bundle are p
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-f8ww-m74w-j9mq ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.