Adversarial Fork - Pools with more than one node as leader slot
Name ID Blocks
[0FEE] 0 FEE #1 15c7b5f50d25fe58fd5c6af53c5341830fca37786790f38e1365f969b4980783 #390443
[CAB] Cardanobay Stakepool 8eb9b5a0cd4ca781eaca806d6a77c891f73dec5bf9f3ec5dae531c50accde5a5 #391200
[KTN3] KATANA 515edfa301325bf8fc2c68adf2e0f73e3ea3bd46676037f1c6b374100e546847 #390641
[EVIL] evilpool 5c098031635cd091a6ba3760c49584e710ca3cd716878db0011261084b572c12 #391181
Other - Network attacking
Name ID Blocks

Adversarial forks - when one pool have multiple instances with same keys and is creating more than one block

Data source: our own research from multiple nodes + datafeed by - thanks Carp!