[New Rule] Python Path File (pth) Creation

[Aegrah]

Summary

This rule detects the creation of .pth files in system-wide and user-specific Python package directories, which can be abused for persistent code execution. .pth files automatically execute Python code when the interpreter starts, making them a stealthy persistence mechanism. Monitoring these paths helps identify unauthorized modifications that could indicate persistence by an attacker or malicious package injection.

Telemetry

[github-actions]

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

• Detailed description of the rule.
• List any new fields required in ECS/data sources.
• Link related issues or PRs.
• Include references.

Rule Metadata Checks

• creation_date matches the date of creation PR initially merged.
• min_stack_version should support the widest stack versions.
• name and description should be descriptive and not include typos.
• query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
• min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
• index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
• integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
• setup should include the necessary steps to configure the integration.
• note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
• tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
• threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

• building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
• bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

• Provide evidence of testing and detecting the expected threat.
• Check for existence of coverage to prevent duplication.

[tradebot-elastic]

⛔️ Tests failed:

• ❌ Python Path File (pth) Creation (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[terrancedejesus]

cc @eric-forte-elastic --> Thoughts on these one from a wheel or common package dependency libraries perspective?

[tradebot-elastic]

⛔️ Tests failed:

[tradebot-elastic]

⛔️ Tests failed:

[DefSecSentinel]

LGTM

[tradebot-elastic]

⛔️ Tests failed:

[tradebot-elastic]

⛔️ Tests failed:

• ❌ Python Path File (pth) Creation (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta
  • events_validation_missing: Not tested with events

[tradebot-elastic]

⛔️ Tests failed:

• ❌ Python Path File (pth) Creation (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta
  • events_validation_missing: Not tested with events

[Aegrah]

Due to the effort required to find/test all PTH creation paths for Windows/macOS, I will not be adding support to these platforms. I created an issue to track this, in case a maintainer from these platforms wants to tackle this. For now, I will just merge the PR for Linux only. cc @w0rk3r @DefSecSentinel. Issue: #4505