254
South Korean telecom company attacks torrent users with malware
(www.tomshardware.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Jun 2024
254 points (98.5% liked)
Technology
59454 readers
1976 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
I don't really understand the attack vector the ISP is using, unless it's exploiting some kind of flaw in higher-level software than BitTorrent itself.
A torrent should be identified uniquely by a hash in a magnet URL.
When a BitTorrent user obtains a hash, as long as it's from an https webpage, the ISP shouldn't be able to spoof the hash. You'd have to either get your own key added to a browser's keystore or have access to one of the trusted CA's keys for that.
Once you have the hash, you should be able to find and validate the Merkle hash tree from the DHT. Unless you've broken SHA and can generate collisions -- which an ISP isn't going to -- you shouldn't be able to feed a user a bogus hash tree from the DHT.
Once you have the hash tree, you shouldn't be able to feed a user any complete chunks that are bogus unless you've broken the hash function in BitTorrent's tree (which I think is also SHA). You can feed them up to one byte short of a chunk, try and sandbag a download, but once they get all the data, they should be able to reject a chunk that doesn't hash to the expected value in the tree.
I don't see how you can reasonably attack the BitTorrent protocol, ISP or no, to try and inject malware. Maybe some higher level protocol or software package.
Some software check for updates without requiring the packages to be signed. The ISP could do a HTTP redirect to a fake torrent client update. The program says “Update available”. It downloads a malicious version.
Other ISPs have been caught injecting adverts into their traffic. So there’s ways.
On the other hand: HTTPS
HTTPS would prevent advert injection, assuming you didn’t accept a bad certificate at any point. But if they control your router and infrastructure, they can still redirect you to other pages however they want.