Important Notice
This is the dump of the 2.4.3 warden vs flo's bot.
root@destro [~]# wardenchk -d wow.exe -dIQ "/flo/*"
> Locating memory PAE
> Reloading for double pass of location
> Locating memory PAE
> SUCCESS!
> Dumping........
> MD5 Compare 1 of 530
> Waiting........................................... ............
> HALTED
> Restarted
> ...........................
> Warden location changed
> New warden compare hashed 530 of 542
> Checking detection patterns
> 542/542
> 12 new warden memory footprints located
> Dumping log..................
> Complete!
root@destro [~]# wardenrep --latest *.EP
> Loading log file
> Log file loaded
> No detection of SHA-1 to SHA-512
> File name search was included!
> Read final report
> Dumping to 00343222552252.EP
Well it appears warden is only looking for the FLO.* filenames, simply renaming them at this point should resolve any issues with automated banning via warden.