read about mirai work (from wiki:
Mirai then identifies vulnerable IoT devices using a table of more than 60 common factory default usernames and passwords)
see opened ports
add 1 + 2 + 3
tip: getting pi-hole admin password for web interface - wrong path
Done all that…
Got 4 open ports… SSH, DNS,HTTP, UPNP…
I even managed to get to the admin page of pi-hole interface once but then it blocked my access…
dont use pi-hole web inferface (web interface is wrong path), use other other interface as port for manage
u can manage with using upnp ? maybe dns ? maybe other ?
read about mirai work (from wiki:
Mirai then identifies vulnerable IoT devices using a table of more than 60 common factory default usernames and passwords)
see opened ports
add 1 + 2 + 3
tip: getting pi-hole admin password for web interface - wrong path
Done all that…
Got 4 open ports… SSH, DNS,HTTP, UPNP…
I even managed to get to the admin page of pi-hole interface once but then it blocked my access…
dont use pi-hole web inferface (web interface is wrong path), use other other interface as port for manage
u can manage with using upnp ? maybe dns ? maybe other ?
@3mrgnc3 said:
Nobody said that. What was that mirai list made up of? What is the logic behind how Mirai spreads? Can you apply that same logic here?
That list was made of 60 default usernames and passwords used by devices.
Mirai scanned the IOT devices find open ports adn try to bruteforce them using the pre caluclated table of usernames and passwords.
The mirai had a computed list of devices with their default usernames and passwords, whenever it scanned a new device it will try to login using the default credentials.