A Bloomberg report recently said that the US is investigating allegations by former Meta contractors that its personnel can access WhatsApp messages despite claiming end-to-end encryption for all messages and calls. Citing law enforcement records, the report said that the former contractors claim that “they and some Meta staff had “unfettered” access to WhatsApp messages — were being examined by special agents with the US Department of Commerce”. The company has now responded to the report calling it “false”.

What WhatsApp says

WhatsApp has denied the investigation, calling reports ‘false’.“This is false. The U.S. Bureau of Industry and Security has disavowed this purported investigation, calling its own employee’s allegations unsubstantiated. What these individuals claim is not possible because WhatsApp, including contractors, cannot access people’s encrypted communications.”The Bloomberg report quoted a Meta spokesperson Andy Stone who said in an email: “What these individuals claim is not possible because WhatsApp, its employees, and its contractors, cannot access people’s encrypted communications”The report further said that as per the records, the contractors claimed that they worked with the Bureau of Industry and Security (BIS) but did not explain what legal theory underpins the inquiry.BIS denied the claims of investigation saying their ’employee’s assertions about WhatsApp encryption practices are unsubstantiated and outside the scope of his authority as an export enforcement agent,” as quoted in the report. “BIS is not investigating WhatsApp or Meta for violations of the export laws,” a BIS spokesperson said.

WhatsApp denies Google’s warning to Android users

Separately, a Forbes report claimed that Google has found a serious WhatApp vulnerability that “opens up (an) attack surface”. WhatsApp clarified on X, writing: “No, Google did not warn Android users. We work with Google to fix reported bugs and improve software for both WhatsApp and Android – exactly how responsible security work helps everyone. This issue was fixed late last year.”