Pakistan Intelligence Hacked Over 70,000 Personal Details Leaked by @G3NTbl4ck

pakistan-intelligence_logo A hacker who uses the handle @G3NTbl4ck has managed to breach a Pakistani Job Site which is titled Pakistan Intelligence ( The breach has happened a few days ago with first what was s simple defacement but now it turns out over 2GB of personal details from people registered and entered in to the sites data base has been leaked. The site’s title is some what misleading but it has nothing really to do with Intelligence gathering besides the storage of personal details of employee’s and employers within Pakistan The hacker left a short message on the defacement which was originally the about page for the site.

oHai all….time to look for a job using some other service…we haz ALL UR infoz…Y?… cuz i can…and U b33n sold out by poor security

pakistan-intelligence First the defacement was announced on the 21st then shortly after another tweet was made with a small sample of whats to come. > @cyber_war_news @thehackersnews @hackread so i haz deface and many users infoz… dump later — #Ag3ntBlack (@G3NTbl4ck) May 21, 2013

On the 24th the leak was announced from the hackers twitter account and comes in the format of a 2.2GB log file from the result of the database extraction and was uploaded to anonpaste as a 24mb compressed file. > @cyber_war_news @hackread still defaced and here is the leak:… 2.2GB log zipped #HACKED — #Ag3ntBlack (@G3NTbl4ck) May 24, 2013

After much playing around i figured a nice easy way to split this file up using GSplit 3.0.1 which works wonders with a little bit of tweaking in the settings. The leak file contains credentials such as full names, addresses, job types, skill types, contact information such as telephone numbers, addresses and more. The data also contains 1 administration account with username and encrypted password. In total there is 76030 rows of personal credentials. A breach like this can be bad for many different people with the shear amount of personal details leaked.

About the author: Lee J

Security Analyst, Developer, OSINT,

Comments are closed.