Business

16 billion logins exposed, including Google, Apple, potentially any online service

Researchers found 30 datasets containing a combined 16 billion logins, most likely coming from infostealer malware

You may want to dedicate some time this weekend to updating your passwords. Researchers discovered 30 exposed datasets online that contain a combined 16 billion login credentials — equivalent to roughly two leaked logins for every person on earth.

Researchers working for Cybernews discovered the datasets, reporting that only one of the 30 found so far had been previously reported. The exposed datasets so far contain anywhere from tens of millions to over 3.5 billion records, with the datasets containing, on average, 550 million exposed records.

However, Cybernews reports there is a small silver lining in that the datasets were only exposed temporarily — just long enough for researchers to find them, but not long enough to find who was controlling them. Researchers suspect some databases might be controlled by other researchers, but some are likely controlled by cybercriminals. The temporary exposure may have allowed bad actors to get at the databases as well.

Researchers said that leaked datasets contained a mix of data acquired from infostealer malware, credential stuffing sets, and repackaged leaks. They also say it’s likely the datasets have overlapping records given the sheer number of records present, but it’s not possible to tell just how many people or accounts were actually exposed, or how many duplicate records there are (though there are bound to be lots).

Moreover, the scale makes it difficult to say which online services are impacted, though researchers did find credentials for major sites like Apple, Facebook, Google, Github, Zoom, Twitch, and more. The good news is that there doesn’t appear to be a centralized breach of these companies, but instead seems to come from infostealer malware. Regardless, the scale of the leak potentially opens the door to any online service.

Cybernews says that leaks of this scale fuel all kinds of attacks, like phishing campaigns and account takeovers. The unknowns surrounding the data — such as who owns it — make the situation even worse.

Ultimately, anyone with online accounts should take some time to update their passwords just in case and enable additional security features like multi-factor authentication (MFA). When updating passwords, it’s highly recommended to use strong, unique passwords and to avoid reusing passwords across multiple services (that way, if one service is breached, your other accounts will be safe). The best way to do this is to use a password manager. Alternatively, using passkeys could also help secure accounts.

Both Apple and Google have password managers built into their devices and software, but if you want to use a third-party service that works across ecosystems easily Bitwarden is a great option.

Beyond updating passwords and enabling extra security features, everyone should be on high alert for suspicious activity and scams. Watch out for suspicious activity on your accounts and report it. Further, watch out for fake communications, like texts or emails, and avoid clicking any links and handing out any personal information.

Source: Cybernews

MobileSyrup may earn a commission from purchases made via our links, which helps fund the journalism we provide free on our website. These links do not influence our editorial content. Support us here.

Related Articles

Fatal error: Uncaught Aws\S3\Exception\PermanentRedirectException: Encountered a permanent redirect while requesting https://ms-staging-baselayer-static-assets.s3.ca-central-1.amazonaws.com/?list-type=2&delimiter=%2F&prefix=uploads%2Fwpcf7_uploads%2F. Are you sure you are using the correct region for this bucket? in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php:49 Stack trace: #0 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(209): Aws\S3\PermanentRedirectMiddleware->Aws\S3\{closure}(Object(Aws\Result)) #1 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(158): GuzzleHttp\Promise\Promise::callHandler(1, Object(Aws\Result), NULL) #2 /var/www/html/vendor/guzzlehttp/promises/src/TaskQueue.php(52): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}() #3 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(163): GuzzleHttp\Promise\TaskQueue->run() #4 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(189): GuzzleHttp\Handler\CurlMultiHandler->tick() #5 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(251): GuzzleHttp\Handler\CurlMultiHandler->execute(true) #6 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(227): GuzzleHttp\Promise\Promise->invokeWaitFn() #7 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #8 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #9 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #10 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #11 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(69): GuzzleHttp\Promise\Promise->waitIfPending() #12 /var/www/html/vendor/aws/aws-sdk-php/src/AwsClientTrait.php(58): GuzzleHttp\Promise\Promise->wait() #13 /var/www/html/vendor/aws/aws-sdk-php/src/ResultPaginator.php(151): Aws\AwsClient->execute(Object(Aws\Command)) #14 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(52): Aws\ResultPaginator->valid() #15 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(69): Aws\map(Object(Aws\ResultPaginator), Object(Closure)) #16 [internal function]: Aws\flatmap(Object(Aws\ResultPaginator), Object(Closure)) #17 /var/www/html/wp-content/plugins/s3-uploads/inc/class-stream-wrapper.php(695): Generator->valid() #18 [internal function]: S3_Uploads\Stream_Wrapper->dir_readdir() #19 /var/www/html/wp-content/plugins/contact-form-7/includes/file.php(362): readdir(Resource id #734) #20 /var/www/html/wp-includes/class-wp-hook.php(322): wpcf7_cleanup_upload_files() #21 /var/www/html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #22 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #23 /var/www/html/wp-includes/load.php(1280): do_action('shutdown') #24 [internal function]: shutdown_action_hook() #25 {main} thrown in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php on line 49