MAL-2026-17586
Vulnerability from ossf_malicious_packages
RubyGems runs this gem's native extension script ext/bitcoin-address-utils/extconf.rb during gem install. The script exits without action on CI runners and sandboxes, based on CI environment variables, the hostname, the username and the working directory. It continues if the system uptime is over 30 minutes and the home directory holds .ssh, .gitconfig, .npmrc, .gem/credentials or .bundle. It then decodes a Base64 Ruby payload and forks twice into a detached process. After 20 to 40 minutes the payload downloads http://45.138.12.177:8092/wgkit.tar.gz to /tmp/.w1.tgz with curl, extracts it to /tmp/.w1/, runs wg_install.sh with bash and deletes both. The payload stores the URL XOR-encoded with the key usv\x9a. The Ruby code in lib/ is a decoy. The RubyGems account reqthrottle_3474 published this gem and 41 others with the same loader on 2026-10-05.
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (8af579a1726db72e88f7c1755ebdec49a2d0a944d0e42a0fb36566d70d751e17)
The gem's native-extension build script extconf.rb, which runs automatically during gem install, decodes a base64-wrapped Ruby payload that XOR-decodes a hardcoded URL (approximately http://45.13.8.12:8092/wgkit.tar.gz, overridable via ENV['WG_KIT_URL']), downloads a tarball to /tmp/.w1.tgz, extracts it, and executes the embedded wg_install.sh via bash. Execution is double-forked and detached so it survives after the install process exits. The shipped C extension source is a two-line empty stub, so the extension exists only to run the dropper. The script contains anti-analysis gating: it refuses to execute inside CI, on ephemeral or sandbox hosts, under usernames matching /uA\d+|sandbox|tester|analys|scanner/, on analysis paths such as /tmp, /var/tmp, /opt/rubygems, /workspace, and on hosts with uptime below 1800 seconds, and only detonates when developer-signal files exist (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle). A 20-40 minute random sleep precedes execution. The attacker-controlled endpoint is a bare IP on a non-standard port with no pinning, hash verification, or TLS, and the staged payload is executed from a hidden /tmp path.
Source: ossf-package-analysis (0e34b9330507c41270304fc7fe17d13b100981d8a39160d0b1ab7fe3eb255077)
The OpenSSF Package Analysis project identified 'bitcoin-address-utils' @ 1.0.0 (rubygems) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
{
"affected": [
{
"database_specific": {
"cwes": [
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"evidence_files": [
{
"path": "ext/bitcoin-address-utils/extconf.rb",
"sha256": "e3fe48a5380287af90961e6e2f9a10157608ea280fe6a7620ff95d5b720c256b",
"tlsh": "b051ca568b8395f54db1d0d044795412fb66bb0d6078ac64f3de0868bb5af2ac4f02fd"
}
]
}
},
"package": {
"ecosystem": "RubyGems",
"name": "bitcoin-address-utils"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
},
{
"contact": [
"https://github.com/ossf/package-analysis",
"https://openssf.slack.com/channels/package_analysis"
],
"name": "OpenSSF: Package Analysis",
"type": "FINDER"
},
{
"contact": [
"https://safedep.io"
],
"name": "SafeDep",
"type": "FINDER"
}
],
"database_specific": {
"iocs": {
"files": [
{
"digests": {
"sha256": "e3fe48a5380287af90961e6e2f9a10157608ea280fe6a7620ff95d5b720c256b"
},
"note": "Native extension script that RubyGems runs at install time. It gates on the environment and starts the payload.",
"paths": [
"ext/bitcoin-address-utils/extconf.rb"
],
"source": "PACKAGE_ARCHIVE"
},
{
"note": "Second-stage archive and install script downloaded and run by the payload.",
"paths": [
"/tmp/.w1.tgz",
"/tmp/.w1/wg_install.sh"
],
"source": "DROPPED"
}
],
"ips": [
"45.138.12.177"
],
"urls": [
"http://45.138.12.177:8092/wgkit.tar.gz"
]
},
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-021055",
"import_time": "2026-10-05T16:22:55.234359619Z",
"modified_time": "2026-10-05T15:57:38Z",
"sha256": "8af579a1726db72e88f7c1755ebdec49a2d0a944d0e42a0fb36566d70d751e17",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
},
{
"import_time": "2026-10-06T00:50:53.737380895Z",
"modified_time": "2026-10-05T07:15:36Z",
"sha256": "0e34b9330507c41270304fc7fe17d13b100981d8a39160d0b1ab7fe3eb255077",
"source": "ossf-package-analysis",
"versions": [
"1.0.0"
]
}
]
},
"details": "RubyGems runs this gem\u0027s native extension script `ext/bitcoin-address-utils/extconf.rb` during `gem install`. The script exits without action on CI runners and sandboxes, based on CI environment variables, the hostname, the username and the working directory. It continues if the system uptime is over 30 minutes and the home directory holds `.ssh`, `.gitconfig`, `.npmrc`, `.gem/credentials` or `.bundle`. It then decodes a Base64 Ruby payload and forks twice into a detached process. After 20 to 40 minutes the payload downloads `http://45.138.12.177:8092/wgkit.tar.gz` to `/tmp/.w1.tgz` with `curl`, extracts it to `/tmp/.w1/`, runs `wg_install.sh` with `bash` and deletes both. The payload stores the URL XOR-encoded with the key `usv\\x9a`. The Ruby code in `lib/` is a decoy. The RubyGems account `reqthrottle_3474` published this gem and 41 others with the same loader on 2026-10-05.\n\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (8af579a1726db72e88f7c1755ebdec49a2d0a944d0e42a0fb36566d70d751e17)\nThe gem\u0027s native-extension build script extconf.rb, which runs automatically during `gem install`, decodes a base64-wrapped Ruby payload that XOR-decodes a hardcoded URL (approximately http://45.13.8.12:8092/wgkit.tar.gz, overridable via ENV[\u0027WG_KIT_URL\u0027]), downloads a tarball to /tmp/.w1.tgz, extracts it, and executes the embedded wg_install.sh via bash. Execution is double-forked and detached so it survives after the install process exits. The shipped C extension source is a two-line empty stub, so the extension exists only to run the dropper. The script contains anti-analysis gating: it refuses to execute inside CI, on ephemeral or sandbox hosts, under usernames matching /uA\\d+|sandbox|tester|analys|scanner/, on analysis paths such as /tmp, /var/tmp, /opt/rubygems, /workspace, and on hosts with uptime below 1800 seconds, and only detonates when developer-signal files exist (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle). A 20-40 minute random sleep precedes execution. The attacker-controlled endpoint is a bare IP on a non-standard port with no pinning, hash verification, or TLS, and the staged payload is executed from a hidden /tmp path.\n\n## Source: ossf-package-analysis (0e34b9330507c41270304fc7fe17d13b100981d8a39160d0b1ab7fe3eb255077)\nThe OpenSSF Package Analysis project identified \u0027bitcoin-address-utils\u0027 @ 1.0.0 (rubygems) as malicious.\n\nIt is considered malicious because:\n\n- The package executes one or more commands associated with malicious behavior.\n",
"id": "MAL-2026-17586",
"modified": "2026-10-06T00:52:41.992057162Z",
"published": "2026-10-05T07:15:36Z",
"references": [
{
"type": "PACKAGE",
"url": "https://rubygems.org/gems/bitcoin-address-utils/versions/1.0.0"
},
{
"type": "REPORT",
"url": "https://safedep.io/rubygems-crypto-gems-install-time-reverse-shell/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in bitcoin-address-utils (RubyGems)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.