Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in zz-oai-test12 (RubyGems)

Malicious code was discovered in the zz-oai-test12 package on RubyGems. The package was identified and cataloged by the OpenSSF malicious packages project.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Limited to direct consumers of the zz-oai-test12 package on RubyGems.
Ecosystems
Attack vectors
Affected entities
  • zz-oai-test12

A malicious package named zz-oai-test12 was published to the RubyGems package repository. The package contained malicious code and was identified as part of the OpenSSF's malicious packages tracking effort.\n\nThe incident was disclosed on July 18, 2026, and documented in GitHub Advisory GHSA-6r2m-cmpq-xcx4. The OpenSSF maintains a public repository of known malicious packages to help the community identify and avoid compromised dependencies.\n\nAny Ruby application that installed this package should be considered potentially compromised and should be audited for unauthorized changes or data exfiltration."

Indicators of compromise

Packages
  • zz-oai-test12

Remediation

  • Remove the zz-oai-test12 package from all affected Ruby projects
  • Audit application logs and system activity for any suspicious behavior during the period the malicious package was installed
  • Review and rotate any credentials or secrets that may have been exposed
  • Update to a clean version of any legitimate package if zz-oai-test12 was intended as a dependency
  • Monitor for similar typosquatting or malicious package attempts targeting your projects

Sources

  1. GitHub Advisory GHSA-6r2m-cmpq-xcx4 · GitHub Advisory Database

Cite this entry

"Malicious code in zz-oai-test12 (RubyGems)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 18, 2026; last updated July 18, 2026. https://supplychainattack.org/incident/malicious-code-in-zz-oai-test12-rubygems-1kcsz0

Suggest a correction

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

  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