supply chain event / NVI-00010534 / Revision 1
Malicious code in keccka (RubyGems)
GitHub lists this malware advisory for keccka. 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.
keccka
source listed= 1.0.0
## Source: amazon-inspector (e4f005ef5a4a20f9aadcdd2c6e78e6d68bb52765b2f5fac2abee6abd7dd261c5) The gem's native extension is a cover: ext/keccka/keccka.c is an empty stub and extconf.rb — auto-executed by `gem install` — contains a base64-wrapped Ruby payload decoded and passed to eval. The payload XOR-decodes a hardcoded C2 URL (http://45.138.12.177:8092/wgkit.tar.gz), curls the tarball over plain HTTP to a bare IP, and runs `bash /tmp/.w1/wg_install.sh` from the extracted content. Execution is gated by anti-analysis checks: it skips when CI environment variables are set (CI, GITHUB_ACTIONS, TRAVIS, JENKINS_URL, GITLAB_CI, CODESPACES), when the hostname matches ephemeral/sandbox patterns (firecracker, sandbox, vagrant), when the username looks generated (sandbox, tester, analys, scanner, uA\d+), when the working directory is an analysis path (/tmp, /opt/rubygems, /workspace), or when system uptime is under 1800 seconds, and it requires developer-looking signals on disk (~/.ssh, ~/.gitconfig, ~/.gem/credentials). On a matching host it double-forks a detached child that sleeps 20-40 minutes before fetching and executing. The destination is a plaintext, unauthenticated bare-IP host u
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-9c95-4459-6pcw ↗
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.