NYT Reveals Online Leakage Of Twitter Source Code

0
6

It has been revealed, quoting a legal document, that parts of Twitter‘s source code—the computer code that runs the social network—was posted online.

According to the New York Times, the incident exposed a significant amount of Twitter‘s intellectual property.

The incident has been described as a rare occurrence.

The source code leak reportedly occurred as Mr. Elon Musk’s company was attempting to fix technical problems and turn around its financial situation.

The filing claims that Twitter acted to have the exposed code removed on Friday by alerting GitHub, a website for software developers where the code was posted.

Though it was not immediately clear how long the leaked code had been available online, reports indicate that it had been available for months before GitHub complied with Twitter’s request and removed the code.

The microblogging service further asked that GitHub be required to reveal the identity of the person who shared the code by the United States (US) District Court for the Northern District of California.

According to sources with knowledge of the situation, executives in charge of the case have determined that whoever was behind the leak left the San Francisco-based company last year.

Since Musk acquired control of Twitter for $44 billion in October 2022, about 75 per cent of its employees have lost their jobs.

The executives were allegedly only recently informed of the source code leak, according to the sources.

One problem, according to them, is that the code contains security holes that could be exploited by hackers or other determined individuals to steal user data or shut down the website.

-All Rights Reserved-
Permission to use any material, including text, still photograph, audio and video from this site is granted subject to permission being formally sought and, if granted, appropriate credit must duly be given to The News Room as the source.

LEAVE A REPLY

Please enter your comment!
Please enter your name here
Captcha verification failed!
CAPTCHA user score failed. Please contact us!