Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in zwtestabc1 (RubyGems)

Malicious code was discovered in the zwtestabc1 RubyGems package. The package was identified and cataloged by the OpenSSF malicious packages project.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
All users of the zwtestabc1 RubyGems package
Ecosystems
RubyGems
Attack vectors
Compromised package
Affected entities
  • zwtestabc1RubyGems package

The zwtestabc1 package on RubyGems was found to contain malicious code. This incident was identified and documented by the OpenSSF's malicious packages project, which maintains a public catalog of known malicious software supply chain incidents.\n\nThe package was published on RubyGems and posed a risk to any Ruby developers who installed or used it. The malicious code discovery was credited to the OpenSSF, indicating this was part of their ongoing efforts to identify and track malicious packages across open source ecosystems.\n\nThe incident was disclosed on July 18, 2026, and has been cataloged under the identifier MAL-2026-9910 in the OpenSSF's malicious packages repository.

Indicators of compromise

Packages
  • zwtestabc1

Remediation

  • Remove zwtestabc1 from all Gemfiles and dependency specifications
  • Audit any systems that may have installed or executed code from zwtestabc1
  • Update to a safe version if a legitimate replacement package exists
  • Review application logs for any suspicious activity that may have resulted from the malicious package
  • Consider using dependency scanning tools to detect similar malicious packages in your supply chain

Sources

  1. GitHub Advisory GHSA-mmhg-xqr2-m6v2 · GitHub Advisory Database

Cite this entry

"Malicious code in zwtestabc1 (RubyGems)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 18, 2026; last updated July 18, 2026. https://supplychainattack.org/incident/malicious-code-in-zwtestabc1-rubygems-14pi3g

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

Related incidents

  1. resolvedcritical

    Malicious code in zzfadgivar05 (RubyGems)

    Malicious code was discovered in the zzfadgivar05 RubyGems package. The package was identified by the OpenSSF malicious packages project and reported via GitHub Advisory GHSA-3gfr-fq7v-cc26.

    RubyGemsCompromised package
  2. resolvedcritical

    Malicious code in zzjinavcsgit (RubyGems)

    Malicious code was published in the zzjinavcsgit RubyGems package. The package was identified and cataloged by the OpenSSF malicious packages project.

    RubyGemsCompromised package
  3. resolvedcritical

    Malicious code in zztest17785553702 (RubyGems)

    Malicious code was discovered in the RubyGems package zztest17785553702. The package was identified and cataloged by the OpenSSF malicious packages project.

    RubyGemsCompromised package
  4. resolvedcritical

    Malicious code in zzpdfvar01 (RubyGems)

    Malicious code was discovered in the zzpdfvar01 RubyGems package. The package was identified by the OpenSSF malicious packages project and assigned identifier MAL-2026-9958.

    RubyGemsCompromised package