• Three Password Cracking Techniques and How to Defend Against Them

    From TCOB1@618:500/14 to All on Wed Feb 26 12:18:50 2025
    https://thehackernews.com/2025/02/three-password-cracking-techniques-and.html

    Passwords are rarely appreciated until a security breach occurs; suffice to say, the importance of a strong password becomes clear only when faced with the consequences of a weak one. However, most end users are unaware of just how vulnerable their passwords are to the most common password-cracking methods. The following are the three common techniques for cracking passwords and how to defend against them.
    Brute force attack#

    Brute force attacks are straightforward yet highly effective techniques for cracking passwords. These attacks involve malicious actors using automated tools to systematically try every possible password combination through repeated login attempts. While such tools have existed for years, the advent of affordable computing power and storage has made them even more efficient today, especially when weak passwords are used. How it works#

    When it comes to brute force attacks, malicious actors employ a range of tacticsΓÇöfrom simple brute force attacks that test every possible password combination to more nuanced approaches like hybrid and reverse brute force attacks. Each method has a distinct strategy behind it, but the motives behind brute force attacks are the same: to gain unauthorized access to protected data or resources.

    Some popular automated tools for carrying out brute force attacks include:

    John the Ripper: a multiplatform password cracker with support for 15 different operating systems and hundreds of hashes and cipher types
    L0phtCrack: a tool that uses rainbow tables, dictionaries, and multiprocessor algorithms to crack Windows passwords
    Hashcat: a cracking/password recovery utility that supports five unique modes of attack for over 300 highly-optimized hashing algorithms

    Examples#

    Back in August 2021, U.S. mobile operator T-Mobile fell victim to a data breach that started with a brute force attack. The security compromise resulted in the exposure of over 37 million customer records containing sensitive data like social security numbers, driver's license information, and other personally identifiable data.
    Defense measures#

    Users should choose strong, complex passwords and multi-factor authentication (MFA) to protect against brute force attacks. Administrators should implement account lockout policies and continuously audit their Windows environments for weak and breached passwords. Tools like Specops Password Auditor can automate these processes across expansive IT environments. Dictionary attack#

    In a password dictionary attack, cyber attackers try to gain access by using a list of common passwords or words from a dictionary. This predefined word list typically includes the most often used words, phrases, and simple combinations (i.e., "admin123"). Password dictionary attacks underscore the importance of complex, unique passwords, as these attack types are especially effective against weak or easily guessable passwords. How it works#

    The process starts with compiling a list of potential passwords from data breaches, common password lists, or publicly available resources. Using an automated tool, malicious actors perform a dictionary attack, systematically testing each password against a target account or system. If a match is found, the hacker can gain access and carry out subsequent attacks or movements. Examples#

    Malicious actors used password dictionaries to crack hashed passwords in several high-profile security incidents, such as the 2013 Yahoo data breach and the 2012 LinkedIn data breach. This allowed them to steal the account information of billions of users.
    Defense measures#

    When creating or resetting passwords, users should use a combination of letters, numbers, and special characters, and avoid using common words or easily guessable phrases. Administrators can implement password complexity requirements in their policies to enforce these mandates across the organization.
    Rainbow table attacks#

    A rainbow table attack uses a special table (i.e., a "Rainbow Table) made up of precomputed strings or commonly used passwords and corresponding hashes to crack the password hashes in a database. How it works#

    Rainbow table attacks work by exploiting chains of hashing and reduction operations to efficiently crack hashed passwords. Potential passwords are first hashed and stored alongside their plaintext counterparts in the rainbow table, then processed with a reduction function that maps them to new values, resulting in a chain of hashes. This process is repeated multiple times to build the rainbow table. When hackers obtain a hash list, they can reverse lookup each hash value in the rainbow tableΓÇöonce a match is identified, the corresponding plaintext password is exposed. Examples#

    While salting (a method of adding random characters to passwords before hashing) has reduced the effectiveness of rainbow table attacks, many hashes remain unsalted; additionally, advances in GPUs and affordable hardware have eliminated the storage limitations once associated with rainbow tables. As a result, these attacks continue to be a likely tactic in current and future high-profile cyber-attacks.
    Defense measures#

    As mentioned previously, salted hashes have significantly reduced the effectiveness of precomputed tables; organizations should therefore implement strong hashing algorithms (e.g., bcrypt, scrypt) in their password processes. Administrators should also regularly update and rotate passwords to reduce the likelihood of rainbow table dictionary matches/hits.

    In short, passwords aren't perfect, but complex and sufficiently long passphrases remain a vital first line of defense against advanced password-cracking techniques. Tools like Specops Policy provide an extra layer of protection by continuously scanning Active Directory against a database of over 4 billion breached passwords.

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1: https/binkd/telnet binkd.rima.ie (618:500/14)
  • From digimaus@618:618/1 to TCOB1 on Wed Feb 26 17:27:09 2025
    TCOB1 wrote to All <=-

    Passwords are rarely appreciated until a security breach occurs;

    I get a kick out of running lastb and look at the strange names people use
    to try to break in my system.

    Most of the names are expected, like "root", "ubuntu", "admin", and such.

    Some of the names are weird...

    ===
    root ssh:notty 194.0.234.37 Wed Feb 26 12:16 - 12:16 (00:00) bin ssh:notty 92.255.57.132 Wed Feb 26 12:09 - 12:09 (00:00) hcg ssh:notty 2.57.122.192 Wed Feb 26 12:05 - 12:05 (00:00) hcg ssh:notty 2.57.122.192 Wed Feb 26 12:05 - 12:05 (00:00) liumiao ssh:notty 2.57.122.192 Wed Feb 26 11:57 - 11:57 (00:00) liumiao ssh:notty 2.57.122.192 Wed Feb 26 11:57 - 11:57 (00:00)
    CH ssh:notty 2.57.122.192 Wed Feb 26 11:49 - 11:49 (00:00)
    CH ssh:notty 2.57.122.192 Wed Feb 26 11:49 - 11:49 (00:00) cs2serve ssh:notty 103.82.93.126 Wed Feb 26 11:46 - 11:46 (00:00) cs2serve ssh:notty 103.82.93.126 Wed Feb 26 11:46 - 11:46 (00:00) ociispth ssh:notty 103.82.93.126 Wed Feb 26 11:44 - 11:44 (00:00) ociispth ssh:notty 103.82.93.126 Wed Feb 26 11:44 - 11:44 (00:00) liangshu ssh:notty 2.57.122.192 Wed Feb 26 11:40 - 11:40 (00:00) liangshu ssh:notty 2.57.122.192 Wed Feb 26 11:40 - 11:40 (00:00) root ssh:notty 103.82.93.126 Wed Feb 26 11:34 - 11:34 (00:00) sun ssh:notty 2.57.122.192 Wed Feb 26 11:32 - 11:32 (00:00) sun ssh:notty 2.57.122.192 Wed Feb 26 11:32 - 11:32 (00:00) root ssh:notty 103.82.93.126 Wed Feb 26 11:32 - 11:32 (00:00)
    mc ssh:notty 103.82.93.126 Wed Feb 26 11:25 - 11:25 (00:00)
    mc ssh:notty 103.82.93.126 Wed Feb 26 11:25 - 11:25 (00:00) wyx ssh:notty 2.57.122.192 Wed Feb 26 11:24 - 11:24 (00:00) wyx ssh:notty 2.57.122.192 Wed Feb 26 11:24 - 11:24 (00:00) debian ssh:notty 92.255.57.132 Wed Feb 26 11:20 - 11:20 (00:00) debian ssh:notty 92.255.57.132 Wed Feb 26 11:20 - 11:20 (00:00) liuwei ssh:notty 2.57.122.192 Wed Feb 26 11:16 - 11:16 (00:00) liuwei ssh:notty 2.57.122.192 Wed Feb 26 11:16 - 11:16 (00:00) masifan ssh:notty 2.57.122.192 Wed Feb 26 11:08 - 11:08 (00:00) ===

    Looks like someone in Romania was bored today.

    The best part is when fail2ban kicks in. I have a very customized install
    of f2b that has a "subnet-recidive" filter in it that blocks problematic subnets for 26 weeks at a time.

    I also have a firewall set up on the BBS box and pfSense as my edge firewall device.

    While there's no perfect solution, no one has ever been successful in
    breaking into my system yet.

    I should change some passwords though...been using them for a long time.

    -- Sean

    ... The trouble with experience is that it sometimes teaches you too late.
    --- MultiMail/Linux
    * Origin: Outpost BBS * Johnson City, TN (618:618/1)
  • From TheCivvie@618:500/14 to digimaus on Fri Feb 28 11:59:18 2025
    digimaus wrote to TCOB1 <=-

    Passwords are rarely appreciated until a security breach occurs;

    I get a kick out of running lastb and look at the strange names people
    use to try to break in my system.

    I got my standard telnet port hit by a russian bot and it just kept recycling all the nodes. BBBS stood up load but it showed the bad firewall in my gateway's firewall. A new 4 thernet port PC has been ordered to become the gateway.


    Most of the names are expected, like "root", "ubuntu", "admin", and such.


    Yeah I got a few of them on telnet

    Looks like someone in Romania was bored today.

    For me it was Russia


    The best part is when fail2ban kicks in. I have a very customized
    install of f2b that has a "subnet-recidive" filter in it that blocks problematic subnets for 26 weeks at a time.

    I also have a firewall set up on the BBS box and pfSense as my edge firewall device.

    While there's no perfect solution, no one has ever been successful in breaking into my system yet.

    I should change some passwords though...been using them for a long time.


    Yeah the gateway I have has a firewall and I think until I opened port 23, it was ok. But opening that showed the lack of a decent firewall on the gateway. It is a decent enough system but a new firewall is being built.

    Sean


    ... TCOB1: https://binkd.rima.ie telnet: binkd.rima.ie:10023

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1: https/binkd/telnet binkd.rima.ie (618:500/14)
  • From Ross Branham@618:100/42 to TheCivvie on Fri Feb 28 08:16:08 2025
    I got my standard telnet port hit by a russian bot and it just kept recycling all the nodes. BBBS stood up load but it showed the bad
    firewall in my gateway's firewall. A new 4 thernet port PC has been ordered to become the gateway.

    The bots have been brutal lately. At times they'll tie up 3 or more nodes trying to get in. Very annoying. I thought about changing the telnet port to a 5 digit number. They don't seem to scan those higher ports.

    |02-=|10Cozmo|02=-

    ... Intelligence tests are biased toward the literate.

    --- Mystic BBS v1.12 A48 (Windows/32)
    * Origin: Lunatics Unleashed (618:100/42)
  • From TheCivvie@618:500/14 to Ross Branham on Fri Feb 28 15:15:20 2025
    Ross Branham wrote to TheCivvie <=-

    I got my standard telnet port hit by a russian bot and it just kept
    recycling all the nodes. BBBS stood up load but it showed the bad
    firewall in my gateway's firewall. A new 4 thernet port PC has been
    ordered to become the gateway.

    The bots have been brutal lately. At times they'll tie up 3 or more nodes trying to get in. Very annoying. I thought about changing the telnet
    port to a 5 digit number. They don't seem to scan those higher ports.


    I changed my firewall to foomuuri and waiting to see how that behaves with BBBS. Trying to get fail2ban to work as well

    TC


    ... TCOB1: https://binkd.rima.ie telnet: binkd.rima.ie:10023

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1: https/binkd/telnet binkd.rima.ie (618:500/14)
  • From Kurt Weiske@618:300/16 to Ross Branham on Sat Mar 1 06:50:56 2025
    Ross Branham wrote to TheCivvie <=-

    The bots have been brutal lately. At times they'll tie up 3 or more
    nodes trying to get in. Very annoying. I thought about changing the
    telnet port to a 5 digit number. They don't seem to scan those higher ports.

    Back around 2015, we got all sorts of red alerts from the infosec team
    at work, it appears one network drop was saturating the network and
    taking it down for the users. We engaged the networking team to try and
    find the location, but ended up going door to door because they didn't
    keep maps of network drops.

    As we walked over to one area, I heard the sound of computer fans at
    full blast - a couple of them. Came over and saw what looked like a
    crypto rig - except it was brute forcing network passwords. Seems that
    the infosec "Sekr1t" team didn't feel they needed to let anyone else in
    IT know, including infosec, and didn't bother doing it outside of
    business hours!



    --- MultiMail/Win v0.52
    * Origin: realitycheckBBS.org -- information is power. (618:300/16)
  • From digimaus@618:618/1 to Kurt Weiske on Sat Mar 1 13:59:00 2025
    Kurt Weiske wrote to Ross Branham <=-

    As we walked over to one area, I heard the sound of computer fans at
    full blast - a couple of them. Came over and saw what looked like a
    crypto rig - except it was brute forcing network passwords. Seems that
    the infosec "Sekr1t" team didn't feel they needed to let anyone else in
    IT know, including infosec, and didn't bother doing it outside of
    business hours!

    That's stupid and ignorant not to mention rude. Did that team think they
    could do whatever they wanted to without accountability?

    -- <8D~

    ... "Well done is better than well said." - Benjamin Franklin
    --- MultiMail/Linux
    * Origin: Outpost BBS * Johnson City, TN (618:618/1)
  • From Kurt Weiske@618:300/16 to digimaus on Sat Mar 1 18:30:43 2025
    Re: Re: Three Password Cracking Techniques and How to Defend Against Them
    By: digimaus to Kurt Weiske on Sat Mar 01 2025 01:59 pm

    That's stupid and ignorant not to mention rude. Did that team think they could do whatever they wanted to without accountability?

    Yeah, they felt like they had blanket approval, seeing as the company had been hacked to the tune of 25,000 employee creds exposed and 120 million user records exposed. The same team that let that happen then took license to break the change control process and do stupid shit like brute-force hacking a domain controller during the day.
    --- SBBSecho 3.23-Win32
    * Origin: realitycheckBBS.org -- information is power. (618:300/16)