I just got the email from haveibeenpwned. F Trello.
this post was submitted on 22 Jan 2024
603 points (97.8% liked)
Technology
59534 readers
3195 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Obligatory: companies should face harsh penalties for this stuff.
This is not something a company did.
The group of people took a list of user names and passwords from a different breach and tried them on trello to see if people used the same password and wrote down which ones did.
Nothing a company can possibly do to stop this, only users can.
Even if the company required 2 factor authentication to fully log in, getting this far would still confirm each account/password combo was correct, which is all the "hackers" did.
This isn't completely true, but it is the current standard.
A website can detect and block many user/password attempts from the same IP and block IPs that are suspicious.
Websites can detect elivated login fails across many IPs are react accordingly (It may be reasonable to block all logins for a time if they detect an attack like this)
I'm sure there are other strategies, I don't know how often they are actually employed, but I wish companies would start taking this sort of attack more seriously (even if it's not at all hacking)
CGNAT would throw a wrench in that when you have thousands of users using mobile data and they appear to be coming from the same ip.
You look for trends, not raw numbers. If an ip increase 500%in 10 minutes... throttle it a bit... insert wait times. If it's trust worthy then allow new value to become normal... otherwise keep the ip throttled.
Nooooo, people keep telling me IPv6 will be insecure because of no longer having NAT.
Mostly people who don't know what a subnet is, but people.
That would be a P1 incident and probably violate SLAs depending on the duration.
Inserting a literally meaningless delay like 5 seconds is sufficient to make your service virtually impenetrable to mass bruteforce/stuffing attacks. Credential stuffing become untenable when your trying to stuff 1million creds with a 5 second cooldown. Most normal users who would hit it would just think their wifi or cell service hicupped.