Technology

Add as a preferred source on Google

About $2,260 in Optimizely-Linked Crypto Payments, Bitquery Estimates

The review tagged 19 Nov. 16 payments as apparently victim-related; Report URI’s earlier $7,040 tally measured tracked wallet receipts, not confirmed losses.

Updated 2 min read
A staff member examines a laptop inside an Optimizely office in New York City. / EconoTimes.ai
A staff member examines a laptop inside an Optimizely office in New York City. / EconoTimes.ai

Bitquery put suspected victim payments tied to Optimizely’s JavaScript incident at about $2,260, below Report URI’s wallet total, which included a transaction linked to the attacker.

Bitquery’s review covered blockchain activity through 1:45 a.m. ET Nov. 17 (06:45 UTC) and treated 19 payments from Nov. 16 as apparent victim payments. Report URI’s earlier tally was about $7,040 in receipts by 2:25 p.m. ET Nov. 16 (19:25 UTC), not verified losses.

Of Report URI’s figure, $4,920 came through stablecoins that passed through a swap. The tracked wallet later received 0.076 Bitcoin (BTC) back; Bitquery tied the return to the attacker’s swap. A separate $51 transfer may have come from the attacker. Leaving it out would put Bitquery’s estimate at about $2,210, but its count still does not align with Report URI’s.

Report URI traced the injected code to a customer-managed “Project JavaScript” field and said Optimizely’s content delivery network served it. The script could substitute a crypto destination on a webpage or in copied text and collect card details submitted in forms. Report URI said it could also capture screenshots and some cookies, and send exploit kits to iOS devices; our earlier coverage of the incident described the reported effects.

Optimizely said an unauthorized party exploited a flaw in its Experimentation product to add JavaScript to some customer projects. The company said it fixed the vulnerability, cleared the injected code from projects, secured affected accounts and added safeguards against unauthorized delivery. The company posted an update at 8:02 p.m. ET Nov. 16 (01:02 UTC Nov. 17) that set the incident’s status to “Monitoring.”

Related articles

View all