The exposure of information connected to more than 41,000 US Department of Homeland Security personnel demonstrates how an employee directory can become an operational map for attackers.
The dataset, published in late October under the name “Icepick,” reportedly contained names, work email addresses, telephone numbers, office locations, job information and internal group memberships. The affected records included personnel associated with Customs and Border Protection, Immigration and Customs Enforcement, US Citizenship and Immigration Services, and the Cybersecurity and Infrastructure Security Agency.
While contact information may appear less sensitive than passwords or Social Security numbers, the combination of identity and organizational metadata creates a significantly broader security risk. It can help attackers understand who works where, which employees may hold privileged access and how different teams are connected.
An ordinary staff directory contains more intelligence than organizations often realize.
Job titles, supervisors, office locations, telephone numbers and internal group names can reveal reporting structures and operational responsibilities. When these details concern law-enforcement, intelligence or cybersecurity personnel, they may also expose individuals connected to sensitive investigations, surveillance systems or undercover work.
Attackers do not necessarily need passwords in the initial leak. Accurate employee information can make subsequent social-engineering attempts substantially more convincing.
A criminal could impersonate an internal help-desk employee and refer to the target’s correct department, manager or office. Another approach could involve impersonating the employee while contacting a colleague, telecommunications provider or external contractor.
The exposed information could consequently support spear-phishing, voice phishing, SIM-swapping attempts, password-reset fraud and targeted harassment.
The group claiming responsibility said the information originated from a DHS identity system associated with Okta. However, Okta said it had found no evidence that its own systems were compromised.
That distinction is important. The appearance of identity-platform data does not automatically mean the platform provider suffered a breach.
Information could potentially be obtained through stolen administrator credentials, compromised endpoints, an improperly protected integration, exported directory records or another system connected to the identity environment. The exact intrusion route has not been publicly established.
Nevertheless, the incident highlights the value of identity infrastructure to attackers. Identity platforms frequently connect employees with cloud applications, administrative tools and internal services. They may contain account attributes, access-group assignments and information about which users can reach particular resources.
Even when passwords are not exposed, this information helps attackers identify valuable accounts and prepare more precise attacks.
Removing the original website or disrupting its domain does not eliminate the exposure.
Once a dataset has been downloaded, it can be copied, mirrored and circulated privately. Employees whose information appeared in the leak may therefore remain at increased risk long after public attention moves elsewhere.
Contact details may also remain useful for years. Employees can change roles while continuing to use the same email addresses or telephone numbers. Historical group memberships and job information can still help attackers understand an agency’s structure or identify people likely to retain valuable professional relationships.
For personnel working in sensitive or public-facing roles, the consequences may extend beyond phishing. The information could enable doxing, threats, physical surveillance or attempts to identify family members and personal accounts.
Responding to this type of exposure requires more than resetting passwords.
Security teams should determine whether authentication tokens, active sessions, application credentials or privileged accounts were accessible through the affected environment. Authentication logs should be reviewed for unusual sign-ins, newly registered devices, unexpected multifactor-authentication changes and access from unfamiliar locations.
Organizations should also examine the information included in their identity directories. Internal group names should not disclose more operational detail than necessary, especially when those names identify sensitive projects, investigative capabilities or administrative privileges.
Other important measures include:
Reviewing privileged and administrative group memberships.
Revoking unnecessary sessions, tokens and application connections.
Requiring phishing-resistant authentication for sensitive accounts.
Monitoring exposed employees for targeted phishing and impersonation.
Restricting bulk exports of identity-directory information.
Separating highly sensitive personnel records from general directories.
Establishing additional protections for undercover and investigative staff.
Reviewing third-party applications connected to identity platforms.
Alerting employees whose details may be used in social-engineering attacks.
Security awareness messages should also be specific to the incident. A general warning about suspicious emails may be inadequate when attackers possess accurate information about an employee’s role, colleagues and workplace.
Organizations commonly apply data-minimization principles to customer information but may overlook internal employee systems.
Identity platforms, human-resources applications and staff directories frequently accumulate information because it is convenient. Each additional attribute increases the intelligence available if an account, integration or export function is compromised.
Organizations should regularly determine which employee attributes are necessary, who can access them and whether they can be exported in bulk. Sensitive operational details should not be stored in broadly accessible identity fields simply because the platform permits it.
The DHS incident illustrates that identity information is not merely administrative data. In the wrong hands, it can reveal an organization’s structure, identify valuable targets and provide the foundation for further attacks.
Protecting identity infrastructure therefore requires securing not only passwords and authentication tokens, but also the metadata surrounding every account.
The incidents were disclosed on October 4 and reveal the risks organizations face when attackers gain access to legitimate employee accounts. Nikkei has not attributed either incident to a specific hacking group or confirmed whether the two attacks were connected.
The more recent incident involved an employee's Microsoft 365 account. According to Nikkei, attackers gained unauthorized access to the account and used it on September 30 to send approximately 9,000 emails.
The messages were sent to people both inside and outside the company. Some recipients were journalistic sources and other individuals who had previously communicated with Nikkei employees.
The emails contained links leading to malicious websites. Because the messages were sent from a legitimate Nikkei employee account, recipients could have been more likely to trust them. This type of account compromise can allow attackers to use an organization's existing relationships to distribute phishing messages.
Nikkei said the incident may have exposed recipients' names and email addresses, along with the contents of some emails. The company is still investigating the number of people whose personal information may have been affected. According to Nikkei, “There may be an increase in emails impersonating Nikkei employees or our group companies,”
Nikkei also disclosed a separate incident involving an employee's Google Workspace account. The account was accessed without authorization beginning in late July.
The company discovered the intrusion in early August after receiving an alert from Google. Nikkei then changed the account's password and said it has not detected any further unauthorized access.
The incident may have exposed information belonging to 1,646 employees and business partners. The potentially affected information included names and email addresses.
Nikkei said the exposed information did not include data related to its readers or journalistic sources. The company also said it has found no evidence that the information was misused.
After the Microsoft 365 incident, Nikkei changed the affected password and contacted recipients of the phishing emails, asking them to delete the messages. The company warned that additional emails impersonating Nikkei employees or its group companies could appear.
Nikkei has also reported the incidents to Japan's data protection authority. Investigations into the scope of the Microsoft 365 compromise and the information potentially exposed are continuing.
Nikkei has experienced other cybersecurity incidents in recent years. In November 2025, the company disclosed a malware-related credential theft incident that potentially exposed information connected to more than 17,000 employees and business partners.
The recent news has notably increased the number of consumers potentially exposed in the incident. “We're deeply saddened to share the news that the recent data breach affects more customers than originally thought,” Trezor said on X.
As per Trezor, the additional 67000 customers placed orders from November 2019 to August 2021.
The leaked data consists of customers' email, phone numbers, names, addresses, order numbers, and shipping addresses. According to Trezor, the data was stored by ShipMonk even though Trezor had earlier received assurance that previous consumer data had been erased.
“Throughout our entire relationship with ShipMonk, we repeatedly requested and received written assurance confirming the deletion of the data, in line with our contract, data policy, and past communications. We are very disappointed that, despite receiving this confirmation, the data was not deleted in their systems,” Trezor said.
According to experts, the breach is not impacting Trezor’s own systems.
Trezor said its hardware wallets are safe and there are no signs that customers’ recovery seed phrases or private keys were breached in the leak.
As per Trezor, “All affected customers have been emailed directly. If you didn’t receive an email, then you are not affected.”
But Trezor and cybersecurity experts are worried that the stolen data could be exploited for social engineering and targeted phishing attacks. Threat actors could misuse customers’ details regarding their Trezor purchases to create scam phone calls or fraud messages.
This can be a serious problem for cryptocurrency users. A threat actor could mimic a company employee if they know someone owns a Trezor wallet and ask the target to verify their wallet or account.
If successful, the attacker could steal the target’s recovery seed phrase, which can allow access to cryptocurrency funds. “Trezor systems were not compromised, and your device is secure. But please be alert for fake emails, phone calls, fraudulent letters, and potential risks to physical security,” the company added.
The announcement comes after the August incident when 13,689 customers had been impacted by the same shipping-provider. At the time, Trezor estimated around 14,000 customers to have been affected by the breach. The recent disclosure of 67,000 suggests the scope of the incident was larger than expected.