A sensitive component iOS source code was leaked by a former Apple intern

  • 314
  •  
  •  
  •  
  • 1
  •  
  •  
  •  
    315
    Shares

According to News, the intern who took the code took it and shared it to a small group of five colleagues in the iOS jailbreaking community in order to help them with their continuing efforts to circumvent Apple’s secured down mobile operating system. The former agent apparently took “all sorts of Apple internal tools and whatnot,” according to one of the individuals who had first received the code, including additional source code that was obviously not included in the initial leak.

The plan was originally to secure that the code never left the original circle of five friends, but apparently, the code flowed beyond the original group sometime last year. Finally, the code was then posted in a Discord chat group and was given to Reddit roughly four months ago although that post was obviously removed by a moderation bot automatically.

But then, it was posted repeatedly to GitHub this week, which is while things snowballed to where they are now, with Apple requesting GitHub to remove the code. According to News, a source at Apple claims that the organization was previously aware of the leak before it made it to GitHub, which would make sense since it appears to have been moved around the jailbreaking community for some time already. Apple itself seems cool about the potential security issues, with the business noting in a statement that the code is already three years old.

Take your time to comment on this article.

The following two tabs change content below.
I am a programmer and tech enthusiast who loves to use my creative skills to solve complex problems. I also love to stay abreast of what is happening in the world of technology, reach me at: [email protected]

Harikrishna Mekala

I am a programmer and tech enthusiast who loves to use my creative skills to solve complex problems. I also love to stay abreast of what is happening in the world of technology, reach me at: [email protected]

Leave a Reply