Data belonging to the multinational telecommunications giant Nokia has been leaked by a threat actor using the username “888.”
The leaked data, allegedly acquired from a breach involving a third party, has been made available for download on a well-known dark web crime forum associated with illegal activities.
According to the threat actor, a breach took place at the company just this month which exposed 7,622 rows of detailed employee information.
Here is a breakdown of the leaked data:
- First Name
- Last Name
- Job Title
- Company Name
- Email Verification Status
- Direct Phone Number
- Corporate Phone Number
- Employees
- Industry
- Person State
- Person Country
- Created Time
From the information provided, it seems that the breach was focused on Nokia's employee database.

Although it is not yet clear how extensive the breach is, the data that has been released indicates that there may be more undisclosed sensitive information that the threat actor has not revealed.
The threat actor in question has a solid reputation within the hacking community and has been responsible for numerous other leaks, including the alleged Microsoft employee data breach.
Nokia, after stopping its own phone manufacturing operations in 2014, has continued to be a major player in the telecommunications industry.
This is thanks to a licensing arrangement with HMD Global, which enables them to produce phones under the Nokia brand.
Nokia's impact in the industry is evident through its impressive $22.81 billion revenue and its role as a leading patent licensor for top mobile phone vendors.
The reported breach raises major questions about the security of Nokia's internal systems and the safeguarding of its employees' personal information.

The leaked data seems to be genuine, as according to our investigation, some names match the profiles of current Nokia employees on LinkedIn. For privacy reasons, we have chosen not to disclose specific names.
Subscribe to our newsletter
There may be a connection between the Microsoft employee breach and this breach, as they both involve the same dataset and field names. It appears that both companies may have experienced a simultaneous data exposure, possibly as a result of a software issue related to data management.