Fluidkey claims that the wallet suffered losses of approximately 1600000 USD, and 52 accounts were affected before they were restored to operation.
BIBIBI
AT A GLANCE
According to PANews's report from Fluidkey, attackers transferred about 1600000 USD from 52 accounts and obtained some user personal information.
Article
Crypto wallet Fluidkey was attacked, resulting in losses of approximately 1600000 USD, affecting 52 accounts
PANews November 22 reports that crypto wallet Fluidkey released a report stating that on November 19, attackers transferred approximately 1600000 USD from 52 unauthorized accounts. The team has suspended transaction processing to prevent further losses and resumed operations on November 20. The attackers exploited two vulnerabilities in the third-party logging tool SigNoz to read internal logs, obtain session tokens for some users, and then forge transfer requests while increasing limits. Private keys on user devices were not leaked; instead, attackers induced users to open the App to trigger signatures and complete transfers. Affected funds spanned six blockchains: Ethereum, Base, BNB Chain, Polygon, Optimism, and Arbitrum. The attackers also obtained some users' personal information. Fluidkey has contacted those affected...
According to a report by Fluidkey on November 22, PANews reported that attackers transferred approximately 1600000 USD from 52 accounts on November 19.
02
The team paused trading operations to prevent further losses, and will resume online on November 20.
03
The report states that attackers exploited two vulnerabilities in the third-party logging tool SigNoz to read internal logs, obtain session tokens for some users, and then forge transfer requests and increase limits.
04
The report states that the private key on the user’s device was not leaked; the attacker triggered the signature process by inducing the user to open the app.
05
The affected funds involve six blockchain networks: Ethereum, Base, BNB Chain, Polygon, Optimism, and Arbitrum.
06
The report states that the attackers also obtained some personal information from users.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
According to the report, the attackers did not transfer funds by stealing the private key on the device. Instead, they first obtained some user session tokens from internal logs, then forged requests, increased limits, and induced users to open the app to trigger a signature process. The fact that the private key was not leaked does not mean that the account funds were not affected.
Why it matters to readers
This incident involves account funds and personal information, and the affected funds are distributed across six chains. Restoring online access is a disclosed progress, but the materials do not indicate whether the losses will be compensated or the vulnerabilities have been fixed.
Do not equate “private key not leaked” or “reached online again” with confirmed financial security; this report clearly describes the path for completing transfers using session tokens and user signatures.
Risks and unknowns
The materials are mere paraphrases of the media’s report on the project party, and no independent verification information is provided.
The original text is cut off at “Fluidkey has contacted the affected...”, so it is impossible to confirm the subsequent notifications and handling details.
No disclosure has been made regarding the compensation plan, the composition of the stolen assets, or the subsequent flow of funds.
It is not specified whether the SigNoz-related vulnerabilities have been fixed, or how the session tokens are handled.
Related Developments
Loading event timeline…
The specific types of personal information obtained and the full scope of impact are not disclosed.
Related concepts
Session token
This term is not in the glossary yet. Browse related concepts in the glossary.