Facebook Tool Lets Users Know if Their Photos Were Compromised in Latest Data Breach

Last week, Facebook reported of a software bug that changed almost 7 million consumers, and this bug may have subjected a broader set of photos to app developers than that which those users planned. The business has confirmed that the faulty API issue was fixed, and that it’s also informed concerned third-party programmers to delete the photos. Programmers will then be able to attain access to the set of photos which would normally happen to be shared. Additionally, the business has now also released a tool which will inform users if their information was compromised or not.
The new help page printed by Facebook will warn users if their accounts has been compromised or not. This new page will require for you to be logged in to the social networking website. For users that have not suffered during the information breach, the following message shows,”Your Facebook account hasn’t been affected by this issue and the programs you use didn’t have access to some other photographs.”

For those affected, the webpage will list all the programs where your photographs were subjected to. Whatever the case, even though your account’s photographs have never been compromised, Facebook recommends logging in to any apps where you’ve shared your Facebook photos to assess which photos they have access to, and invert it if too much information has passed .

The company had previously said that only those people who granted permission for third-party apps to access the photographs were affected. Generally, when folks give apps access to their photographs, it means just photographs posted in their Facebook page. Facebook says the insect possibly gave developers access to additional photographs, such as the ones shared on Marketplace or on Facebook Stories. The insect affected photos that individuals uploaded into Facebook but chose not to post or could not post for technical reasons.

Facebook said that these users’ photos may have been exposed for 12 days in September (between September 13 and 25) and the bug was repaired.


Please enter your comment!
Please enter your name here