Hardware wallet manufacturer Trezor disclosed a data breach affecting nearly 14,000 of its customers after ShipMonk, its shipping provider and logistics partner, got hacked. [...]

Trezor, a manufacturer of hardware cryptocurrency wallets, has disclosed a data breach impacting nearly 14,000 customers. The incident stemmed from unauthorized access to the systems of ShipMonk, Trezor's shipping and logistics partner.
The breach, which Trezor confirmed on Thursday, August 13, 2026, exposed customer order data. This included full names, shipping addresses, email addresses, and phone numbers for 11,742 customers. An additional 1,947 customers had partial exposure, limited to their name, city, and email address.
Customers affected by the breach are located in the United States, the United Kingdom, Sweden, Colombia, Brazil, Italy, and Portugal. The compromised data pertains to orders placed and received between May 10 and August 8, 2026.
Trezor clarified that its own systems were not compromised and that the security of its hardware wallets remains unaffected. The company emphasized that the breach did not impact its operations or services.
However, Trezor warned affected customers to be vigilant against potential phishing attempts. The stolen information could be leveraged by scammers to send fraudulent emails, make fake phone calls, or send deceptive letters, potentially impersonating banks, cryptocurrency exchanges, or even Trezor itself. These sophisticated phishing attempts could aim to trick users into revealing sensitive personal information or their 24-word recovery seeds.
This is not the first data breach disclosed by Trezor. In January 2024, the company reported an incident involving its third-party support ticketing portal. That breach exposed names, usernames, and email addresses of approximately 66,000 users who had interacted with Trezor Support since December 2021. Following that incident, Trezor confirmed that the stolen information was used in phishing attacks designed to trick recipients into divulging their recovery seeds.

JetBrains is urging Cadence users to revoke and rotate all credentials following a security incident last month in which unidentified threat actors exploited a recently disclosed critical vulnerability in TeamCity to breach its own environment. "Cadence users should immediately revoke or rotate all credentials and secrets that may have been used to run their Cadence executions," JetBrains said.
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.

OpenAI has announced a $1 billion commitment to provide subsidized access to its Daybreak AI cybersecurity tools for under-resourced critical infrastructure defenders. The initiative, named Daybreak for Frontline Defenders, will offer AI models, training, and technical support over the next six months, prioritizing water and wastewater utilities, electric grid operators, and local government entities. This move aims to equip organizations with limited budgets and staff against increasingly sophisticated cyber threats.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.