@jerry I'm guessing just another sockpuppet of the original attacker. This kind of pressure from several sockpuppets seems to be part of the MO of the attacker; see the Debian bug in which they were pushing hard for the update to 5.6.1 that fixed the valgrind warning caused by the exploit, with several users who all appear to be sockpuppets: bugs.debian.org/cgi-bin/bugrep