top of page
Search
stomitarthys1975

Password To Pro Facebook Hacker V 1.5: The Only Facebook Hacker You'll Ever Need



In late September 2021, a user of a known hacker forum posted an announcement claiming to possess the personal data of more than 1.5 billion Facebook users. The data is currently up for sale on the respective forum platform, with potential buyers having the opportunity to purchase all the data at once or in smaller quantities.


After accessing the link, they will be redirected to a cloned version of the website the perpetrators pretend to represent. Then, if the user enters their actual current password, the cybercriminals will be able to hijack the affected account.




Password To Pro Facebook Hacker V 1.5



A member of a known forum for hackers claimed to be in possession of the information in late September and offered to sell it in chunks to others on the forum, according to a report from Privacy Affairs. One user claimed to have gotten a quote of $5,000 for the information of 1 million users.


Samples shared by the user appear to have been authentic, according to Privacy Affairs. The outlet also checked the information against previous leaks and found that alleged info was a legitimately new leak, not old data being resold. The hacker claimed to be in charge of a four-year-old data scraping operation with 18,000 clients.


A similar data leak occurred in the spring and affected roughly 533 million users from 106 countries. The information was found to be legitimate by outlets like Business Insider, who used Facebook's password reset feature to partially confirm the phone numbers associated with certain emails.


To conduct this study, Google created a breach notification service and an associated Chrome Password Checkup browser extension that collects anonymous data and hashed logins. When a user logs into a site with the extension installed, the anonymous hash of the login credentials is sent back to Google and checked against 4 billion usernames and passwords that were leaked in data breaches.


Of those users who were notified, only 26% of the warnings resulted in a password change. Of these password changes, though, 60% resulted in the user changing to a more secure password than their original one.


As compromised login credentials could be used in credential stuffing attacks, which is when attackers try to access other sites using leaked logins, it is important to use unique passwords for each site and to quickly change passwords that are exposed.


The full results from Google's study can be found in the "Protecting accounts from credential stuffing with password breach alerting" paper whose results will be presented this week at the USENIX Security Symposium.


On January 19, Paypal sent out data breach notifications to nearly 35,000 customers whose accounts had been improperly accessed. This incident was a credential stuffing attack, in which the hacker leveraged passwords and other data that had been exposed in prior incidents involving other services.


This is a case example of why you should not reuse passwords. If you use the same password across multiple websites, an attacker that steals your password in one data breach (or finds it on the darkweb) can then use across any account that uses the same login credentials.


On January 11, Mailchimp detected a social engineering attack in which a hacker tricked an employee into giving away their account credentials. They proceeded to access 133 user accounts. Mailchimp proceeded to shut down the attack and alert their users that may have been affected.


Following a string of ransom attempts and leaks, a trove of data on over 200 million Twitter users circulated among hackers in December 2022, and was published in full on BreachForums on January 4th. This data includes email addresses, names, and usernames, but does not appear to include passwords or other highly sensitive data.


This data was originally scraped by exploiting an API vulnerability that was exposed from June 2021 to January 2022. This vulnerability was exploited repeatedly by different hacker, and resulted in multiple ransomware attempts and leaks in the latter half of 2022. Most recently, a hacker known as Ryushi attempted to ransom the data for $200,000 in late December.


On November 24th, a hacker published data including email addresses and phone numbers of 5.4 million Twitter users on a hacker forum. This hacker had exploited an API vulnerability in late 2021 to scrape this data, and attempted to sell it for $30,000 in July 2022.


On November 7th, an unidentified hacking group publicly threatened Medibank, the largest health insurance provider in Australia. Claiming to possess data on 9.7 million current and former customers, the hacker said they would publish the data within 24 hours if their demands were not met. Medibank confirmed that nearly 500,000 health claims had also been unlawfully accessed in the breach.


On July 19, 2022, a hacker posted data on 69 million Neopets users for sale on an online forum. The leak included personal data such as name, email address, date of birth, zip code, and more, as well as 460 MB of compressed source code for the Neopets website. The Neopets team confirmed the data breach via Twitter.


Neopets has been breached numerous times over the years. Several hackers and Neopets users have accessed the source code as well as user databases. If you ever used Neopets, it may be wise to delete your account to protect your data from future data breaches.


In July 2022, Marriott International confirmed that hackers had stolen 20 gigabytes of sensitive data in June 2022. The breach apparently resulted form a social engineering attack, in which an anonymous hacking group tricked an employee into granting them access.


In June 2022, Michigan-based Flagstar Bank notified customers of a data breach in which hackers stole the social security numbers of 1.5 million customers. The attack itself occurred in early December 2021, and Flagstar discovered the breach in early June 2022. In response, Flagstar notified law enforcement officials of the breach and hired a cybersecurity firm to help handle the incident.


On March 20, 2022, the hacker group Lapsus$ posted a screenshot to their Telegram channel indicating that they had breached Microsoft. The screenshot was taken within Azure DevOps, a collaboration software created by Microsoft, and indicated that Bing, Cortana, and other projects had been compromised in the breach.


On March 23, a group of hackers exploited a security vulnerablity to loot $540 million in cryptocurrency from the Ronin Network. Most of that money was stolen from Axie Infinity, a popular game that uses cryptocurrency and NFTs. The hackers in question appear to have ties to North Korea.


In February 2022, hackers hijacked GiveSendGo, a Christian fundraising website. They redirected the site to a page condemning the Canadian Freedom Convoy protestors, and posted personal details on the 90,000 people who had donated to the Freedom Convoy via the website.


At one time or another, we have all been frustrated by trying to set a password, only to have it rejected as too weak. We are also told to change our choices regularly. Obviously such measures add safety, but how exactly?


I will explain the mathematical rationale for some standard advice, including clarifying why six characters are not enough for a good password and why you should never use only lowercase letters. I will also explain how hackers can uncover passwords even when stolen data sets lack them.


If you are told to select a 12-character password that can include uppercase and lowercase letters, the 10 digits and 10 symbols (say, !, @, #, $, %, ^, &, ?, / and +), you would have 72 possibilities for each of the 12 characters of the password. The size of the possibility space would then be 7212 (19,408,409,961,765,342,806,016, or close to 19 x 1021).


That is more than 62 trillion times the size of the first space. A computer running through all the possibilities for your 12-character password one by one would take 62 trillion times longer. If your computer spent a second visiting the six-character space, it would have to devote two million years to examining each of the passwords in the 12-character space. The multitude of possibilities makes it impractical for a hacker to carry out a plan of attack that might have been feasible for the six-character space.


For a truly strong password as defined by ANSSI, you would need, say, a sequence of 16 characters, each taken from a set of 200 characters. This would make a 123-bit space, which would render the password close to impossible to memorize. Therefore, system designers are generally less demanding and accept low- or medium-strength passwords. They insist on long ones only when the passwords are automatically generated by the system, and users do not have to remember them.


There are other ways to guard against password cracking. The simplest is well known and used by credit cards: after three unsuccessful attempts, access is blocked. Alternative ideas have also been suggested, such as doubling the waiting time after each successive failed attempt but allowing the system to reset after a long period, such as 24 hours. These methods, however, are ineffective when an attacker is able to access the system without being detected or if the system cannot be configured to interrupt and disable failed attempts.


_________________________________If A = 26 and N = 6, then T = 308,915,776D = 0.0000858 computing hourX = 0; it is already possible to crack all passwords in the space in under an hour_________________________________If A = 26 and N = 12, then T = 9.5 1016D = 26,508 computing hoursX = 29 years before passwords can be cracked in under an hour_________________________________


If A = 100 and N = 10, then T = 1020D = 27,777,777 computing hoursX = 49 years before passwords can be cracked in under an hour_________________________________If A = 100 and N = 15, then T = 1030D = 2.7 1017 computing hoursX = 115 years before passwords can be cracked in under an hour________________________________If A = 200 and N = 20, then T = 1.05 1046D = 2.7 1033 computing hoursX = 222 years before passwords can be cracked in under an hour 2ff7e9595c


1 view0 comments

Recent Posts

See All

コメント


bottom of page