The Web Is Broken – Botnet Part 2
jan.wildeboer.net
The Web Is Broken – Botnet Part 2
1–10 of 301 posts
Re: The Web Is Broken – Botnet Part 2
#2This is nasty in other ways too. What happens when someone uses these B2P residential proxies to commit crimes that get traced back to you?
Anything incorporating anything like this is malware.
Re: The Web Is Broken – Botnet Part 2
#3Are there any lists with known c&c servers for these services that can be added to Pihole/etc?
Re: The Web Is Broken – Botnet Part 2
#4I don't know if I should be surprised about what's described in this article, given the current state of the world. Certainly I didn't know about it before, and I agree with the article's conclusion.
Personally, I think the "network sharing" software bundled with apps should fall into the category of potentially unwanted applications along with adware and spyware. All of the above "tag along" with something the user DID want to install, and quietly misuse the user's resources. Proxies like this definitely have an impact for metered/slow connections - I'm tempted to start Wireshark'ing my devices now to look for suspicious activity.
There should be a public repository of apps known to have these shady behaviours. Having done some light web scraping for archival/automation before, it's a pity that it'll become collateral damage in the anti-AI-botfarm fight.
Re: The Web Is Broken – Botnet Part 2
#5I have some success in catching most of them at https://visitorquery.com
Re: The Web Is Broken – Botnet Part 2
#6Has anyone tried to compile a list of software that uses these libraries? It would be great to know what apps to avoid
Re: The Web Is Broken – Botnet Part 2
#7What is the point of app stores holding up releases for review if they don't even catch obvious malware like this?
Re: The Web Is Broken – Botnet Part 2
#8when the shit hits the fan, this seems like the product.
Re: The Web Is Broken – Botnet Part 2
#9> So if you as an app developer include such a 3rd party SDK in your app to make some money — you are part of the problem and I think you should be held responsible for delivering malware to your users, making them botnet members.
I suspect that this goes for many different SDKs. Personally, I am really, really sick of hearing "That's a solved problem!", whenever I mention that I tend to "roll my own," as opposed to including some dependency, recommended by some jargon-addled dependency addict.
Bad actors love the dependency addiction of modern developers, and have learned to set some pretty clever traps.
Re: The Web Is Broken – Botnet Part 2
#10How is this not just illegal? Surely there’s something in GDPR that makes this not allowed.