nano SIEM
Enrichments

Tor exit nodes

Supported in:Self-hosted

Flag traffic to and from Tor exit relays, using the Tor Project's bulk exit list.

Use Tor exit-node enrichment to identify traffic to and from Tor exits. nano flags matching IPs using the Tor Project's bulk exit list. This list holds only the addresses exits actually use; it has no relay metadata such as nicknames, flags or bandwidth.

A Tor exit is an anonymizer, not a malware indicator. Use it as context: an inbound login from a Tor exit, or an internal host connecting out to one, is worth a look, but Tor use alone isn't proof of compromise.

How it's delivered

The Tor exit list is part of nano's signed platform feed bundle, on open core and Self-run alike. There's nothing to configure and no key. Marketplace shows the feed's state.

What a match writes

When src_endpoint.ip or dst_endpoint.ip is on the exit list, ClickHouse writes tor_exit at ingest:

FieldValue
enrichments.ioc_src_ip_threat_typetor_exit when src_endpoint.ip is an exit
enrichments.ioc_dest_ip_threat_typetor_exit when dst_endpoint.ip is an exit

Events with no match keep these fields empty. There is no tor_exit_node threat type. The same fields carry ThreatFox matches.

Search examples

All Tor traffic:

enrichments.ioc_src_ip_threat_type="tor_exit" OR enrichments.ioc_dest_ip_threat_type="tor_exit" | stats count by src_endpoint.ip, dst_endpoint.ip

Internal hosts connecting out to Tor exits:

enrichments.ioc_dest_ip_threat_type="tor_exit" | stats count, dc(dst_endpoint.ip) as exits by src_endpoint.ip, device.hostname

Successful logins from Tor:

class_uid=3002 status_id=1 enrichments.ioc_src_ip_threat_type="tor_exit" | table time, user.name, src_endpoint.ip, metadata.log_source

Detection example

class_uid=3002 status_id=1 enrichments.ioc_src_ip_threat_type="tor_exit"
| stats count, values(src_endpoint.ip) as exits by user.name
| risk score=60 entity=user.name factor="Successful login from a Tor exit node"

Troubleshoot

Need help with these checks? Contact support with the request ID and time with timezone.

A Tor match is missing

Confirm that the event's IP is on the bulk exit list and mapped to src_endpoint.ip or dst_endpoint.ip. Then check the feed state in Marketplace; an expired feed no longer stamps new events.

What's next

On this page