w002yardprobe
Affected
- Versions:
0.0.4,0.0.5
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 w002yardprobe (RubyGems)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (721580f8eda44ad5ee7604f5ba0648e8830302f784e3e4a995e02ca7359c909e)
The gem ships a .yardopts file containing --load./script.rb, which causes YARD to execute script.rb whenever documentation is generated for the gem (locally via yard doc, in CI, or on doc-hosting services such as RubyDoc.info). script.rb collects host identifiers — Socket.gethostname, current working directory, UID, and RUBY_VERSION — and POSTs them via Net::HTTP.post_form to the hardcoded third-party collector https://webhook.site/97fa3c6a-3fad-4d2d-8312-15dc37e41e66. The same script also rewrites lib/w002yardprobe.rb in place (substituting a MARKSLOT token with a runtime stamp) and drops sentinel files W002SCRIPT_RAN.txt and W002EGRESS_OK.txt in the detected build directory (e.g. /build), indicating the gem is instrumented to probe a documentation-build sandbox. The package self-identifies as a probe; the exfiltration and build-environment mutation are the gem's purpose. The trigger is YARD doc generation rather than gem install or require, so the harm materializes against whichever host (developer workstation, CI runner, or doc-hosting pipeline) processes the gem's documentation.
Not rated by the source.
0.0.4, 0.0.5None 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