Skip to content

Add checks to avoid SYSCALL.SCRIPT false positives #265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 23, 2025

Conversation

hillu
Copy link
Collaborator

@hillu hillu commented Apr 23, 2025

Likely reasons for nonsensical SCRIPT enrichments:

  • Missing PATH messages in the audit log, so the code would not look at the "item=0" element
  • Empty PATH.name
  • major(PATH.dev) = 0, probably due to bind mounts by container runtimes

Likely reasons for nonsensical SCRIPT enrichments:

- Missing PATH messages in the audit log, so the code would not look
  at the "item=0" element
- Empty PATH.name
- major(PATH.dev) = 0, probably due to bind mounts by container
  runtimes
@hillu hillu merged commit 619cedb into threathunters-io:master Apr 23, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant