1200KM / sigma-rule
Sign-In From Malware Infected IP — Sigma Rule
Sigma rule 821b4dc3-1295-41e7-b157-39ab212dd6bd. Sign-In From Malware Infected IP — Sigma Rule. Indicates sign-ins from IP addresses infected with malware that is known to actively communicate with a bot server.
Rule metadata and linked tags
Author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo'. Source status: test; severity: high. Source dates: 2023-09-03 / not supplied.
{
"product": "azure",
"service": "riskdetection"
}Pinned original Sigma rule · Detection Rule License 1.1
Source SHA-256: 834d289c647351381b55cbd7f96d8b37415f3da7027449c1d577f73c4b801cee
Detection logic
Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.
title: Sign-In From Malware Infected IP
id: 821b4dc3-1295-41e7-b157-39ab212dd6bd
status: test
description: Indicates sign-ins from IP addresses infected with malware that is known to actively communicate with a bot server.
references:
- https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-risks#malware-linked-ip-address-deprecated
- https://learn.microsoft.com/en-us/entra/architecture/security-operations-user-accounts#unusual-sign-ins
author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo'
date: 2023-09-03
tags:
- attack.t1090
- attack.command-and-control
logsource:
product: azure
service: riskdetection
detection:
selection:
riskEventType: 'malwareInfectedIPAddress'
condition: selection
falsepositives:
- Using an IP address that is shared by many users
level: high
False positives
- Using an IP address that is shared by many users
Source references
Connected ecosystem references
Exact source-tagged techniques
Telemetry review
Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.