mal-2026-869
Vulnerability from ossf_malicious_packages
Published
2026-02-12 08:10
Modified
2026-02-19 22:47
Summary
Malicious code in ritch (PyPI)
Details

-= Per source details. Do not edit below this line.=-

Source: kam193 (bc0d5c6c0c3175de2d5def02fe422574cfee5f7fe3a88f894de7122aa9dcf588)

Package is a typosquatting or dependency confusion attempt with a low-harm local-only action, like leaving a flag file.


Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-local-typosquatting

Reasons (based on the campaign):

  • dependency-confusion

  • The package overrides the install command in setup.py to execute malicious code during installation.

  • typosquatting

Source: ossf-package-analysis (53836e778fae351105bebc4ec62937db1766d236b1ab050c142e8a57d863c7ea)

The OpenSSF Package Analysis project identified 'ritch' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "ritch"
      },
      "versions": [
        "1.0.0"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "https://github.com/kam193",
        "https://bad-packages.kam193.eu/"
      ],
      "name": "Kamil Ma\u0144kowski (kam193)",
      "type": "REPORTER"
    },
    {
      "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": [
      {
        "id": "pypi/GENERIC-local-typosquatting/ritch",
        "import_time": "2026-02-12T09:22:04.910454194Z",
        "modified_time": "2026-02-12T08:45:10.233987Z",
        "sha256": "bc0d5c6c0c3175de2d5def02fe422574cfee5f7fe3a88f894de7122aa9dcf588",
        "source": "kam193",
        "versions": [
          "1.0.0"
        ]
      },
      {
        "import_time": "2026-02-19T22:45:34.84688713Z",
        "modified_time": "2026-02-12T08:10:35Z",
        "sha256": "53836e778fae351105bebc4ec62937db1766d236b1ab050c142e8a57d863c7ea",
        "source": "ossf-package-analysis",
        "versions": [
          "1.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: kam193 (bc0d5c6c0c3175de2d5def02fe422574cfee5f7fe3a88f894de7122aa9dcf588)\nPackage is a typosquatting or dependency confusion attempt with a low-harm local-only action, like leaving a flag file.\n\n\n---\n\nCategory: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research \u0026 co, with clearly low-harm possibilities.\n\n\nCampaign: GENERIC-local-typosquatting\n\n\nReasons (based on the campaign):\n\n\n - dependency-confusion\n\n\n - The package overrides the install command in setup.py to execute malicious code during installation.\n\n\n - typosquatting\n\n## Source: ossf-package-analysis (53836e778fae351105bebc4ec62937db1766d236b1ab050c142e8a57d863c7ea)\nThe OpenSSF Package Analysis project identified \u0027ritch\u0027 @ 1.0.0 (pypi) 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-869",
  "modified": "2026-02-19T22:47:48Z",
  "published": "2026-02-12T08:10:35Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://bad-packages.kam193.eu/pypi/package/ritch"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in ritch (PyPI)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…