With the new security issues with data breaches, the addon now records the username the bot used to try to log in. You can research these usernames in the ACP and see if they are real users accounts. If they are, I suggest locking them ASAP so the real user will have to verify their email next time they actually log in.
Feature Request:
Additional column called "Actions" with a dropdown of actions for each entry you can perform, based on the data. Like "Reset password" (of that user), "Ban user", "Block IP" (afaik there's a built-in funtion in XF) or maybe even an own, configurable action, like "Block IP in firewall" - and you can specify an address in spaminator config which URL should be called, like https://myforum.tld/firewalltools/blockip.php?url=$URL
Last line might be optional / too difficult, but that would improve the workflow of administrative antispam actions
Now That Ive got your attention: This is a beta release, take a full backup before installing on a production site. Optimally try it out on a test site that is a replication of your live site before installing on the live site...