MAL-2026-18436
Vulnerability from ossf_malicious_packages – Published: 2026-11-01 10:15 – Updated: 2026-11-02 02:18 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| RubyGems |
macs-shoaibs-pro17
|
90002.1
|
The gem declares ext/mkrf_conf.rb as a native extension, which RubyGems auto-executes during gem install. The script contains no mkmf/rake build logic (no create_makefile, have_header, or compiler invocation). Instead it reads /etc/passwd, /etc/hosts, /etc/resolv.conf, the hostname, the current user, and the working directory, opens a TLS connection via TCPSocket to d5jjaycuhgtrskqh1n53qo70ur0kobc0.oastify.com:443 (a Burp Collaborator subdomain), and POSTs the collected data to that host before writing a.installed marker. The gemspec summary ("A simple gem for demonstration purposes") does not correspond to any functionality present in the package.
The OpenSSF Package Analysis project identified 'macs-shoaibs-pro17' @ 90002.1 (rubygems) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
| Type | Indicator | Hashes |
|---|---|---|
| Evidence file |
ext/mkrf_conf.rb
|
sha256
d0d53b5bdb14b9b6bbb54cf381bd929d86fc8cbd796c14a4cf1bbc85f05b5716tlsh
3011658993987ca05b9ac86fe20c304160e7cd4bc50a6531bb8a0de0cf6db3c63316f9 |
| Package archive |
macs-shoaibs-pro17-90002.1.gem
|
sha256
42250485012302d3e623177f20965a9e566ee2bcb942056614a95c824163d0b3 |
- CWE-506 - Embedded Malicious Code
| URL | Tags |
|---|---|
| https://rubygems.org/gems/macs-shoaibs-pro17/vers… | PACKAGE |
{
"affected": [
{
"database_specific": {
"cwes": [
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"evidence_files": [
{
"path": "ext/mkrf_conf.rb",
"sha256": "d0d53b5bdb14b9b6bbb54cf381bd929d86fc8cbd796c14a4cf1bbc85f05b5716",
"tlsh": "3011658993987ca05b9ac86fe20c304160e7cd4bc50a6531bb8a0de0cf6db3c63316f9"
}
],
"package_integrity": [
{
"filename": "macs-shoaibs-pro17-90002.1.gem",
"hashes": {
"sha256": "42250485012302d3e623177f20965a9e566ee2bcb942056614a95c824163d0b3"
}
}
]
}
},
"package": {
"ecosystem": "RubyGems",
"name": "macs-shoaibs-pro17"
},
"versions": [
"90002.1"
]
}
],
"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"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"import_time": "2026-11-01T10:35:43.320256405Z",
"modified_time": "2026-11-01T10:15:35Z",
"sha256": "b839ba696947a26e059bc82d4feb35120e11ff4885ff5bc5da19d9800f51f837",
"source": "ossf-package-analysis",
"versions": [
"90002.1"
]
},
{
"id": "IN-MAL-2026-022480",
"import_time": "2026-11-02T02:17:04.6085334Z",
"modified_time": "2026-11-02T01:56:00Z",
"sha256": "0c7ce0186e7517c1df32cfd61177f90bee77d43a19d7c3963cc657e07109123a",
"source": "amazon-inspector",
"versions": [
"90002.1"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (0c7ce0186e7517c1df32cfd61177f90bee77d43a19d7c3963cc657e07109123a)\nThe gem declares ext/mkrf_conf.rb as a native extension, which RubyGems auto-executes during `gem install`. The script contains no mkmf/rake build logic (no create_makefile, have_header, or compiler invocation). Instead it reads /etc/passwd, /etc/hosts, /etc/resolv.conf, the hostname, the current user, and the working directory, opens a TLS connection via TCPSocket to d5jjaycuhgtrskqh1n53qo70ur0kobc0.oastify.com:443 (a Burp Collaborator subdomain), and POSTs the collected data to that host before writing a.installed marker. The gemspec summary (\"A simple gem for demonstration purposes\") does not correspond to any functionality present in the package.\n\n## Source: ossf-package-analysis (b839ba696947a26e059bc82d4feb35120e11ff4885ff5bc5da19d9800f51f837)\nThe OpenSSF Package Analysis project identified \u0027macs-shoaibs-pro17\u0027 @ 90002.1 (rubygems) as malicious.\n\nIt is considered malicious because:\n\n- The package communicates with a domain associated with malicious activity.\n",
"id": "MAL-2026-18436",
"modified": "2026-11-02T02:18:22.979869373Z",
"published": "2026-11-01T10:15:35Z",
"references": [
{
"type": "PACKAGE",
"url": "https://rubygems.org/gems/macs-shoaibs-pro17/versions/90002.1"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in macs-shoaibs-pro17 (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
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
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.