Facebook Bug That Automatically Sent Friend Requests to Other Users Resolved: Report

Facebook was reportedly affected by a bug that automatically sent a friend request to other users, an issue that the company says it has resolved. Users recently took to Twitter to complain that the social networking service was sending requests to users immediately upon visiting their profile. The issue was spotted by several users, weeks after the company laid off over 11,000 employees, or 13 percent of its workforce — mostly comprising engineers and adjacent tech teams in its second round of layoffs this year.

On Friday, users began complaining that Facebook was automatically sending a friend request to a user as soon as you visited their profile. Twitter user Bavid Mcjavid (@bavidmcjavid) shared a screen recording of the glitch that shows the Facebook app selecting the Add friend button without any user input, forcing the user to manually cancel the friend request.

Several other users on Twitter complained of the same glitch, and one user stated that every person they “stalked” — viewing a profile privately without informing the user — automatically received a request from them. Another user also said they were experiencing the same issue, adding that it was the “wrong night” to go through their yearbook to stalk other users.

Shortly after the glitch was detected, Majavid tweeted that the issue seemed to have been resolved. Meanwhile, Meta shared a statement with The Daily Beast, revealing that it had fixed a bug that caused the issue and apologised for the issue. 

“We fixed a bug related to a recent app update that caused some Facebook friend requests to be sent mistakenly. We’ve stopped this from happening and we apologize for any inconvenience this may have caused,” a Meta spokesperson told the Daily Beast.

The glitch that caused Facebook to send requests to other users upon visiting their profile comes around a month after Meta announced its second round of layoffs this year. As part of Meta CEO Mark Zuckerberg’s “Year of Efficiency”, the company is prepared to lay of thousands of employees and cut costs using various methods — including lower bonus payouts for some employees — by the end of the year. 


Google I/O 2023 saw the search giant repeatedly tell us that it cares about AI, alongside the launch of its first foldable phone and Pixel-branded tablet. This year, the company is going to supercharge its apps, services, and Android operating system with AI technology. We discuss this and more on Orbital, the Gadgets 360 podcast. Orbital is available on Spotify, Gaana, JioSaavn, Google Podcasts, Apple Podcasts, Amazon Music and wherever you get your podcasts.
Affiliate links may be automatically generated – see our ethics statement for details.



Check out our Latest News and Follow us at Facebook

Original Source

iOS 16 ‘Mailjack’ Bug Causes Mail App to Crash Upon Receiving Maliciously Crafted Email: All Details

An iOS 16 bug is reportedly causing the Mail application on iPhone and iPad models that have been updated to the latest version of Apple’s operating system to crash, rendering it inaccessible. The bug comes in the form of an otherwise routine-looking mail message, that has an unusual sender field that includes extra characters that causes the Mail application to crash on iOS 16. The bug has been dubbed “Mailjack” and allows any outsider to lock iPhone and iPad users out of their email accounts with a modified email.

The crash-triggering email was identified by Equinux’s VPN Tracker. Generally, the “From” field has the sender’s name followed by their email address in the syntax — From: sender@example.com. However, the crash-triggering email had the from field syntax as — From: “”@example.com. Mail services like Gmail, Outlook, and Hotmail automatically rewrite such inbound emails with unusual syntax to prevent such triggers.

While Gmail and Yahoo have filters in place to block these maliciously crafted emails altogether, Apple’s first-party iCloud Mail does not appear to have any such rewriting or filtering mechanisms in place, as per the report.

The current solution to avoiding the trigger is to delete the message from the inbox or spam folder from a device that is running an older iOS version or via an external email client. Users may also choose to move the trigger email to another subfolder on an IMAP email account. However, navigating to the respective subfolder will cause the application to crash again according to the website. Admins may also choose to add the syntax “”@example.com to their list of blocked emails via email security software or firewall.

Equinux’s VPN Tracker has created a dedicated webpage where users can test the bug trigger by entering their email address. However, users are advised not to try this as it could lock them out of their emails unless they have access to an older iOS or external email client to delete the triggering message.


Check out our Latest News and Follow us at Facebook

Original Source

Exit mobile version