Urgent.News

What's breaking now, across thousands of outlets.

Tech

Europe hit by another wave of grocery store freezer hacks

The new incidents come weeks after a cyberattack on fridges and freezers in France that forced supermarkets to throw away food.

Europe is experiencing another wave of grocery store freezer hacks, with refrigeration issues affecting stores in Sweden and Belgium. The problems echo a recent cyberattack that targeted French supermarkets, forcing supermarkets to discard food. Swedish supermarket chains ICA and Coop have confirmed cooling problems at several of their stores.

Coop reported that seven out of its over 800 stores were affected overnight, and they are managing the situation. ICA's spokesperson said an overnight incident impacted the refrigeration and freezer systems of a small number of its stores. Staff were unable to adjust the temperature, with some freezers set to 50 degrees Celsius.

In Belgium, Delhaize, a retail company, confirmed an IT incident affecting refrigeration systems in some of its stores, with one manager having to discard the contents of her fridges and freezers. No connection between the French attack and the current disruptions has been established, making this a developing story.

Written by urgent.news from Business Insider's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at businessinsider.com →

More in Tech

Nibnib says 4bpp. The file still has a header.

My tiny nibnib file was larger than the raw RGB image I fed into it. For a 16×16 synthetic gradient, the raw RGB pixels took 768 bytes . The nibnib file took 1,220 bytes .

  • nibnib file size 1,220 bytes for 16×16 gradient, compared to 768 bytes for raw RGB
  • File stores dimensions and fixed palette before row data with explicit pixel pairs
  • nibnib version 0.1.0 used, independent reader verified documented layout and decoder

My parser read past the input. AddressSanitizer stayed quiet.

I gave a deliberately broken parser three bytes. It read byte four. AddressSanitizer said nothing. Then I changed the allocation around the input.

  • Parser read beyond input's fourth byte
  • AddressSanitizer failed to detect error
  • Fix involves allocating space for zero

More from Monday 2 November →