You could also send a specific string to a channel, which caused mIRC to log it to a file. Then a hyper-sensitive anti-virus would see it and quarantine mirc.exe :D
Probably EICAR. AV engines are only supposed to fire on EICAR when the file contains only magic string, but many are/were trigger happy and will alert if it appears anywhere.
It did indeed, though people used to hide their IP addresses through various means, and so CTCP was usually a sure fire winner.
Most cheap modems seemed to ignore the required 1 second (IIRC) delay. Well-heeled users who could afford U.S. Robotics et al were safe, winmodem users were not.
You could also send a specific string to a channel, which caused mIRC to log it to a file. Then a hyper-sensitive anti-virus would see it and quarantine mirc.exe :D
Probably EICAR. AV engines are only supposed to fire on EICAR when the file contains only magic string, but many are/were trigger happy and will alert if it appears anywhere.
https://en.wikipedia.org/wiki/EICAR_test_file
Also seemed to work over ICMP ping, with "+++ATH0M0DT112", they did not return to the channel.
I think it was some buggy Rockwell modem chips that did not require the delay between +++ and switching to command mode, but it has been some decades.
It did indeed, though people used to hide their IP addresses through various means, and so CTCP was usually a sure fire winner.
Most cheap modems seemed to ignore the required 1 second (IIRC) delay. Well-heeled users who could afford U.S. Robotics et al were safe, winmodem users were not.