PH_Rule_SIGMA_1768
Enabled
Detects initiated network connections to crypto mining pools. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/network_connection/net_connection_win_crypto_mining_pools.yml
7
Security
Impact
Impact consists of techniques that adversaries use to disrupt availability or compromise integrity by manipulating business and operational processes. Techniques used for impact can include destroying or tampering with data. In some cases, business processes can look fine, but may have been altered to benefit the adversaries’ goals. These techniques might be used by adversaries to follow through on their end goal or to provide cover for a confidentiality breach.
https://attack.mitre.org/tactics/TA0040T1496
Resource Hijacking
Adversaries may leverage the resources of co-opted systems in order to solve resource intensive problems which may impact system and/or hosted service availability. One common purpose for Resource Hijacking is to validate transactions of cryptocurrency networks and earn virtual currency. Adversaries may consume enough system resources to negatively impact and/or cause affected machines to become unresponsive.(Citation: Kaspersky Lazarus Under The Hood Blog 2017) Servers and cloud-based(Citation: CloudSploit - Unused AWS Regions) systems are common targets because of the high potential for available resources, but user endpoint systems may also be compromised and used for Resource Hijacking and cryptocurrency mining.
https://attack.mitre.org/techniques/T1496Server
Windows Sysmon via FortiSIEM Agent
Correlation
No remediation guidance specified
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
Filter
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType REGEXP "Win-Sysmon-3-Network-Connect.*" AND destName IN ("alimabi.cn","ap.luckpool.net","bcn.pool.minergate.com","bcn.vip.pool.minergate.com","bohemianpool.com","ca.minexmr.com","ca.monero.herominers.com","cbd.monerpool.org","cbdv2.monerpool.org","cryptmonero.com","crypto-pool.fr","crypto-pool.info","cryptonight-hub.miningpoolhub.com","d1pool.ddns.net","d5pool.us","daili01.monerpool.org","de.minexmr.com","dl.nbminer.com","donate.graef.in","donate.ssl.xmrig.com","donate.v2.xmrig.com","donate.xmrig.com","donate2.graef.in","drill.moneroworld.com","dwarfpool.com","emercoin.com","emercoin.net","emergate.net","ethereumpool.co","eu.luckpool.net","eu.minerpool.pw","fcn-xmr.pool.minergate.com","fee.xmrig.com","fr.minexmr.com","hellominer.com","herominers.com","huadong1-aeon.ppxxmr.com","iwanttoearn.money","jw-js1.ppxxmr.com","koto-pool.work","lhr.nbminer.com","lhr3.nbminer.com","linux.monerpool.org","lokiturtle.herominers.com","luckpool.net","masari.miner.rocks","mine.c3pool.com","mine.moneropool.com","mine.ppxxmr.com","mine.zpool.ca","mine1.ppxxmr.com","minemonero.gq","miner.ppxxmr.com","miner.rocks","minercircle.com","minergate.com","minerpool.pw","minerrocks.com","miners.pro","minerxmr.ru","minexmr.cn","minexmr.com","mining-help.ru","miningpoolhub.com","mixpools.org","moner.monerpool.org","moner1min.monerpool.org","monero-master.crypto-pool.fr","monero.crypto-pool.fr","monero.hashvault.pro","monero.herominers.com","monero.lindon-pool.win","monero.miners.pro","monero.riefly.id","monero.us.to","monerocean.stream","monerogb.com","monerohash.com","moneroocean.stream","moneropool.com","moneropool.nl","monerorx.com","monerpool.org","moriaxmr.com","mro.pool.minergate.com","multipool.us","myxmr.pw","na.luckpool.net","nanopool.org","nbminer.com","node3.luckpool.net","noobxmr.com","pangolinminer.comgandalph3000.com","pool.4i7i.com","pool.armornetwork.org","pool.cortins.tk","pool.gntl.co.uk","pool.hashvault.pro","pool.minergate.com","pool.minexmr.com","pool.monero.hashvault.pro","pool.ppxxmr.com","pool.somec.cc","pool.support","pool.supportxmr.com","pool.usa-138.com","pool.xmr.pt","pool.xmrfast.com","pool2.armornetwork.org","poolchange.ppxxmr.com","pooldd.com","poolmining.org","poolto.be","ppxvip1.ppxxmr.com","ppxxmr.com","prohash.net","r.twotouchauthentication.online","randomx.xmrig.com","ratchetmining.com","seed.emercoin.com","seed.emercoin.net","seed.emergate.net","seed1.joulecoin.org","seed2.joulecoin.org","seed3.joulecoin.org","seed4.joulecoin.org","seed5.joulecoin.org","seed6.joulecoin.org","seed7.joulecoin.org","seed8.joulecoin.org","sg.minexmr.com","sheepman.mine.bz","siamining.com","sumokoin.minerrocks.com","supportxmr.com","suprnova.cc","teracycle.net","trtl.cnpool.cc","trtl.pool.mine2gether.com","turtle.miner.rocks","us-west.minexmr.com","usxmrpool.com","viaxmr.com","webservicepag.webhop.net","xiazai.monerpool.org","xiazai1.monerpool.org","xmc.pool.minergate.com","xmo.pool.minergate.com","xmr-asia1.nanopool.org","xmr-au1.nanopool.org","xmr-eu1.nanopool.org","xmr-eu2.nanopool.org","xmr-jp1.nanopool.org","xmr-us-east1.nanopool.org","xmr-us-west1.nanopool.org","xmr-us.suprnova.cc","xmr-usa.dwarfpool.com","xmr.2miners.com","xmr.5b6b7b.ru","xmr.alimabi.cn","xmr.bohemianpool.com","xmr.crypto-pool.fr","xmr.crypto-pool.info","xmr.f2pool.com","xmr.hashcity.org","xmr.hex7e4.ru","xmr.ip28.net","xmr.monerpool.org","xmr.mypool.online","xmr.nanopool.org","xmr.pool.gntl.co.uk","xmr.pool.minergate.com","xmr.poolto.be","xmr.ppxxmr.com","xmr.prohash.net","xmr.simka.pw","xmr.somec.cc","xmr.suprnova.cc","xmr.usa-138.com","xmr.vip.pool.minergate.com","xmr1min.monerpool.org","xmrf.520fjh.org","xmrf.fjhan.club","xmrfast.com","xmrigcc.graef.in","xmrminer.cc","xmrpool.de","xmrpool.eu","xmrpool.me","xmrpool.net","xmrpool.xyz","xx11m.monerpool.org","xx11mv2.monerpool.org","xxx.hex7e4.ru","zarabotaibitok.ru","zer0day.ru")
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
destName,hostName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
destName = Filter.destName,
hostName = Filter.hostName