Good news, there are agencies which looks for these vulnerabilities and report the issues to manufacturers! But, usually the person who makes the botnet patches the vuln. after they infect the device so no one else can take control of it. So, unless the owner of the device apart of the botnet updates software after a fix is implemented and factory resets, nothing can be done to ‘remove’ the device from the botnet.
Finding out the person behind an online device then explain the importance of doing a reset+patch is hard enough for one person. It would have to be done for many thousandd of device on a regular basis. And many devices are setup and forgot, no one manages them.
A block may be an easier and better insentive. It would require an explicit error message. Eg “Connection blocked because malicious activity, likely from compromised device. Here are details about the compromised device model and how to patch…”
Good news, there are agencies which looks for these vulnerabilities and report the issues to manufacturers! But, usually the person who makes the botnet patches the vuln. after they infect the device so no one else can take control of it. So, unless the owner of the device apart of the botnet updates software after a fix is implemented and factory resets, nothing can be done to ‘remove’ the device from the botnet.
Start blacklisting the devices then. People will learn quick that their device is infected if everything stops working for them lol.
That’s the way.
Finding out the person behind an online device then explain the importance of doing a reset+patch is hard enough for one person. It would have to be done for many thousandd of device on a regular basis. And many devices are setup and forgot, no one manages them.
A block may be an easier and better insentive. It would require an explicit error message. Eg “Connection blocked because malicious activity, likely from compromised device. Here are details about the compromised device model and how to patch…”