mal-2026-1019
Vulnerability from ossf_malicious_packages
Published
2026-02-24 16:18
Modified
2026-02-24 17:28
Summary
Malicious code in spark-audit-notify (PyPI)
Details

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

Source: kam193 (1c527925d1e7cb4055b6c154326cd54a713ad543349c2b3b6f8ab8f0d75e8cbe)

During installation, host identification details (including AD domain) are exfiltrated through a series of functions obfuscating this behavior.


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: 2026-02-spark-audit-notify

Reasons (based on the campaign):

  • The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

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

  • obfuscation

Credits

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "spark-audit-notify"
      },
      "versions": [
        "1.30",
        "1.31",
        "1.32"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "https://github.com/kam193",
        "https://bad-packages.kam193.eu/"
      ],
      "name": "Kamil Ma\u0144kowski (kam193)",
      "type": "REPORTER"
    }
  ],
  "database_specific": {
    "iocs": {
      "domains": [
        "us-central1-bucket-438814.cloudfunctions.net"
      ]
    },
    "malicious-packages-origins": [
      {
        "id": "pypi/2026-02-spark-audit-notify/spark-audit-notify",
        "import_time": "2026-02-24T16:51:42.132222628Z",
        "modified_time": "2026-02-24T16:34:45.949671Z",
        "sha256": "1c527925d1e7cb4055b6c154326cd54a713ad543349c2b3b6f8ab8f0d75e8cbe",
        "source": "kam193",
        "versions": [
          "1.30",
          "1.31",
          "1.32"
        ]
      },
      {
        "id": "pypi/2026-02-spark-audit-notify/spark-audit-notify",
        "import_time": "2026-02-24T17:26:58.132648271Z",
        "modified_time": "2026-02-24T16:42:52.440012Z",
        "sha256": "bad29715b2e2b29f662ac9b09aebf597251a1018490cba55cc79d67ffa585929",
        "source": "kam193",
        "versions": [
          "1.30",
          "1.31",
          "1.32"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: kam193 (1c527925d1e7cb4055b6c154326cd54a713ad543349c2b3b6f8ab8f0d75e8cbe)\nDuring installation, host identification details (including AD domain) are exfiltrated through a series of functions obfuscating this behavior.\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: 2026-02-spark-audit-notify\n\n\nReasons (based on the campaign):\n\n\n - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.\n\n\n - The package overrides the install command in setup.py to execute malicious code during installation.\n\n\n - obfuscation\n",
  "id": "MAL-2026-1019",
  "modified": "2026-02-24T17:28:41Z",
  "published": "2026-02-24T16:18:43Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://bad-packages.kam193.eu/pypi/package/spark-audit-notify"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in spark-audit-notify (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…