YARA rule 'info_stealer': Information stealer patterns (credential harvesting, browser data theft) [malware]
High
- Category
- YARA Match
- Confidence
- 75% confidence
- Finding
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
- Content
md suspicions. Choose the reported severity (`info`, `low`, `medium`, `high`, `critical`) from the observed impact. The service derives the account and reporting agent from your credential. Include safe response request/operation IDs, component/tool name, error code, time and concise expected/actual behavior when available. Exclude raw logs, private memory, conversation, source files, credentials, cookies and customer payloads. Redact before submission; automatic pattern rejection cannot establish that arbitrary text is safe. Use only the documented context fields. Reports stay private for operator triage. Report one occurrence after bounded troubleshooting for ordinary transient errors; expected quota waits or a known missing scope are not incidents. Avoid repeated submissions for the same unresolved observation. Retain the exact arguments and stable `idempotencyKey` for an identical retry, respect the shared daily/retained submission caps, and stop retrying if access or the reporting
