November 2, 2026

What happened

Sophos reported that the Aur0ra ransomware group, tracked as GOLD OGRE, used AI agents to move through victim networks, collect credentials and pursue domain-administrator access. [1]

Sophos recovered late-August artifacts from the Cursor AI coding assistant showing attackers supplied AI agents with VPN logins, proxy access, targets and objectives. [2]

The reported workflow included network mapping, but the supplied evidence does not provide further detail because the source span is truncated. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   The group behind the Aur0ra ransomware has been using AI agents to move through victim networks, collect credentials and work its way up to domain administrator access, according to Sophos.

2. [2]

   AI-assisted intrusion workflow (Source: Sophos) The company, which tracks the group as GOLD OGRE, recovered artifacts from the Cursor AI coding assistant in late August that show the attackers handing the agents VPN logins, proxy access, targets and objectives.

3. [3]

   The agents then mapped the network … More → The post Ransomware gang talked AI agents into doing much of its dirty work appeared first on Help Net Security .

Read the original article →

What happened

Researchers discovered VOLTA-AUTODOXER (VOLTA), a Windows infostealer that uses a large language model to rank victims’ stolen data by monetization value. [1]

VOLTA can harvest passwords and cookies from Chromium-based browsers, along with data from Outlook profiles and Slack workspaces. [2]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Cybersecurity researchers have discovered a new Windows infostealer malware called VOLTA-AUTODOXER (aka VOLTA) that makes use of a large language model (LLM) to rank a victim's stolen data by their monetization value.

2. [2]

   Like other typical stealer families, VOLTA is equipped to harvest passwords and cookies from Chromium-based web browsers; data from Outlook profiles and Slack workspaces;

Read the original article →

What happened

Byoky is an open-source wallet for AI API keys offered as Chrome and Firefox extensions and iOS and Android apps. [1]

Users store OpenAI, Anthropic, Google Gemini and other provider keys in Byoky, encrypted on their own device. [2]

Applications request access to stored keys, while Byoky sends each request to the provider itself. [3]

The application receives a session token, while the API key remains in the wallet. [4] [5]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Byoky is an open-source wallet for AI API keys, available as a Chrome and Firefox extension and as iOS and Android apps.

2. [2]

   Users store their keys for OpenAI, Anthropic, Google Gemini and other providers in it, encrypted on their own device.

3. [3]

   Apps that want those keys ask the wallet for access, and the wallet sends each request to the provider itself.

4. [4]

   The app gets a session token.

5. [5]

   The key stays in the wallet.

Read the original article →

What happened

Vinay Thakker, CTO of KloudStax, discusses setting identity, credential, and network limits for AI agents. [1]

Thakker argues that agents should use their own identity, with the person’s identity attached when the agent acts on that person’s behalf. [2]

The interview covers credential-proxy failure points, the first ten lines of a command policy for a coding agent, and preventing data from leaving through package installs. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   In this Help Net Security interview, Vinay Thakker, CTO of KloudStax, explains how to set identity, credentials, and network limits for AI agents.

2. [2]

   He argues that agents should run under their own identity, with the person’s identity attached when acting on someone’s behalf.

3. [3]

   He covers where credential proxies go wrong, what the first ten lines of a command policy for a coding agent should say, and how to stop data from leaving through package installs … More → The post The first ten lines of a command policy for AI coding agents appeared first on Help Net Security .

Read the original article →

What happened

DeepSeek released dsh-superagent as a research prototype that performs work on a GitHub repository. [1]

The agent begins work when an allowed user requests it or when a team-authored rule covers the request. [2]

Why it matters

A chat or GitHub scope can be opened so that anyone in it can request work by mentioning the agent. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Deepseek released a research prototype of dsh-superagent, a coding agent that does work on a GitHub repository for you.

2. [2]

   Who can ask for work The agent gets to work in two situations: an allowed user asks for something, or a rule your team wrote covers it.

3. [3]

   You can also open up a chat or GitHub scope, and then anyone in it can request work just by mentioning the agent.

Read the original article →

What happened

Chainalysis reported that an external actor used offensive agentic techniques to gain unauthorized access to its systems and internal tools, stealing some non-sensitive customer data. [1] [2] [3]

The accessed data included platform user IDs, full names, email addresses, and organization role labels; Chainalysis was still determining which records belonged to each customer. [4] [5] [6] [7]

Based on evidence available to date, Chainalysis found no indication that the attacker accessed investigation content, transaction or query results, clear-text passwords, MFA secrets, or user session tokens. [8] [9] [10]

Chainalysis did not explain how the attack was carried out and said it was patching vulnerabilities, hardening systems, engaging outside cybersecurity experts, and conducting a broader review. [11] [12] [13]

Why it matters

The exposed names and email addresses could be used in phishing campaigns, according to the report. [14]

Known limitations

Chainalysis said it would provide customers with a detailed breakdown of the records accessed after completing its analysis. [5] [7]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Blockchain analytics firm Chainalysis says it was the target of a cybersecurity incident.

2. [2]

   A threat actor accessed its systems and internal tools and stole some non-sensitive customer data.

3. [3]

   “This month, Chainalysis detected an external actor using offensive agentic techniques to gain unauthorized access to Chainalysis systems and internal tools.” reads the statement published by the company, which also includes the full email sent to affected customers.

4. [4]

   According to Chainalysis, attackers gained access to user IDs, full names, email addresses and organization role labels for users on the platform.

5. [5]

   The company is still working out which records belong to which customer and promises a detailed breakdown when it finishes.

6. [6]

   Some non-sensitive customer data, such as user IDs, full names, email addresses, and organization role labels for users provisioned on our platform were accessed, including such information relating to your organization and users.

7. [7]

   We are in the process of determining the records for your organization that were accessed and will provide a detailed breakdown as soon as that analysis is complete.

8. [8]

   So far, Chainalysis has found no sign of access to investigation content such as graphs, notes or cases, or to transaction and query results.

9. [9]

   It also found no clear-text passwords, MFA secrets or user session tokens in the attacker’s hands.

10. [10]

    “Based on the evidence available to date, we have found no indication that these incidents resulted in the unauthorized access of investigation content (such as graphs, notes, or cases), transaction or query results, passwords in clear text, MFA secrets, or user session tokens.” continues the press release.

11. [11]

    However, it did not explain how the attack was carried out.

12. [12]

    “ The company says it’s patching vulnerabilities and hardening its systems around the clock.

13. [13]

    It has hired outside cybersecurity experts and is using large language models to support a wider review that goes beyond the flaws the attacker used.

14. [14]

    Since the exposed data includes names and email addresses, attackers could use it to launch phishing campaigns.

Read the original article →

What happened

The FBI said North Korea was responsible for stealing more than $6 billion in virtual assets from cryptocurrency exchange Binance on or about October 29, 2026. [1] [2]

The FBI published an alert about the attribution on October 31. [2]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   North Korea was behind the theft of more than $6 billion in cryptocurrency from Binance, the FBI has confirmed.

2. [2]

   “The Federal Bureau of Investigation (FBI) is releasing information advising the Democratic People’s Republic of Korea (North Korea) was responsible for the theft of more than $6 billion USD in virtual assets from cryptocurrency exchange Binance, on or about October 29, 2026,” the bureau said in an alert published on October 31.

Read the original article →

What happened

Ukraine and Russia said hackers compromised emergency-alert apps and sent false air-raid, nuclear, radiation, chemical-attack and street-fighting warnings; the claims were not independently confirmed. [1] [2] [3]

Ukraine’s Air Alarm app issued nationwide red-level alerts and additional localized warnings; the Ukrainian ministry temporarily disabled it for maintenance after it was apparently compromised. [4] [5] [6] [7]

Ukraine’s Centre for Countering Disinformation advised users during an app outage to enable smartphone notifications, heed sirens and consult only official sources. [8]

Russia’s emergency ministry said its app suffered a massive cyberattack and that restoration was ongoing, while claiming broader alert channels remained available through sirens, loudspeakers, text messages, television and radio. [12] [13] [14]

Why it matters

The article describes a security trade-off: disabling a compromised alert system can stop false warnings but temporarily remove a channel for genuine emergency information. [9] [10]

The article says shutdowns require reliable backup channels, including sirens, official messaging services and other emergency communication systems. [11]

Known limitations

A Stanford cyber-policy and security scholar told the BBC he believed this was the first incident affecting an official Ukrainian information app and suspected it would recur. [15] [16]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Hackers reportedly hit Ukraine ‘s and Russia ‘s emergency alert apps, sending fake nuclear and attack warnings and raising concerns over public safety.

2. [2]

   Ukraine and Russia both said on Sunday night that hackers had compromised their emergency alert apps and used them to send fake warnings about air raids and other attacks, including nuclear threats.

3. [3]

   The BBC reported the incident, but neither side’s claims have been independently confirmed.

4. [4]

   GMT), Ukraine’s widely used Air Alarm app sent the highest-level air raid warnings across the country.

5. [5]

   Some people, including residents of Kyiv, also received alerts about possible radiation, chemical attacks and street fighting.

6. [6]

   “The Air Alert app is supported by the Ministry of Digital Transformation of Ukraine, and informs users instantly about the beginning and end of defence alerts.

7. [7]

   The ministry said it temporarily disabled the app for maintenance after it had “apparently been compromised”.

8. [8]

   Ukraine’s Centre for Countering Disinformation has advice for when the app isn’t working: turn on smartphone notifications, pay attention to sirens, and read only official sources.

9. [9]

   “While the false alerts were quickly contained, cybersecurity experts suggested it was a new line in apparent Russian cyberattacks.” The temporary shutdown of the Air Alert app also carries significant risks, even if it lasts only a short time.

10. [10]

    The incident also highlights a difficult security trade-off: disabling a compromised alert system may prevent attackers from spreading false warnings, but it can temporarily remove a critical channel for delivering real emergency information.

11. [11]

    Any shutdown therefore needs reliable backup channels, such as sirens, official messaging services and other emergency communication systems.

12. [12]

    A few hours later, Russia’s ministry of emergency situations said its own app had suffered “a massive cyberattack” that sent fake information to the public.

13. [13]

    Russia said it was still restoring the app but claimed the hack had not affected its wider alert system.

14. [14]

    It said people could still receive warnings through sirens, loudspeakers, text messages, TV and radio.

15. [15]

    Although the fake warnings were quickly stopped, experts see the attack as a worrying escalation.

16. [16]

    “I think it’s the first time it’s happened to an official Ukrainian information app, but I suspect it won’t be the last,” Herbert Lin, a senior research scholar for cyber policy and security at Stanford University, told BBC World Service’s Newsday programme.

Read the original article →

What happened

Nick Andersen’s 210-day limit as acting CISA director is nearing, while no permanent nominee has emerged after Sean Plankey withdrew in April and a replacement expected in June failed to materialize four months later. [1] [2] [3] [4]

Multiple sources said the administration may try to keep Andersen in the role by changing his title to “senior official performing the duties of” CISA director. [5]

Andersen has overseen release of a strategy intended to guide CISA through 2030, and Montgomery said Andersen appears to be making plans three to six months ahead. [15] [16] [17] [18]

Why it matters

House Homeland Security Committee leaders and other sources expressed support for Andersen, citing his leadership, improved morale, stability, and continuity at CISA. [6] [7] [8] [9] [10] [11]

Mark Montgomery said a Senate-confirmed CISA director could help the agency compete for priorities in interagency and White House processes; he described retaining Andersen in some capacity as the next-best option if no nominee is confirmed. [12] [13] [14]

Known limitations

DHS publicly supported Andersen’s work but referred further questions to the White House, which did not respond; the reported title change and the identity of any permanent nominee remain unresolved. [2] [3] [5] [19] [20]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   The clock is running out on Nick Andersen’s time to serve as acting director of the Cybersecurity and Infrastructure Security Agency, but there appear to be efforts afoot to keep him in the role for longer, with no permanent nominee in sight.

2. [2]

   Since then, Sean Plankey withdrew his nomination for the Senate-confirmed position in April, and in June, Department of Homeland Security Secretary Markwayne Mullin said a likely replacement nominee had met with the president and was coming soon .

3. [3]

   Four months later, no nominee has materialized.

4. [4]

   The easiest way to keep Andersen in the acting role would be to select a nominee, thus pausing his 210-day limit on serving as acting director, said Mark Montgomery, senior director of the Foundation for Defense of Democracies think tank’s Center on Cyber and Technology Innovation.

5. [5]

   Multiple sources told CyberScoop they’ve been told that the administration has been working to keep Andersen in the job, possibly by shifting his title to “senior official performing the duties of” CISA director.

6. [6]

   On Capitol Hill, the leaders of the House Homeland Security Committee offered at least some degree of support for Andersen.

7. [7]

   “Acting Director Andersen is doing an excellent job preparing CISA to meet today’s threats, and we have a great working relationship.

8. [8]

   “I appreciate our partnership and would gladly support his nomination.” “Acting Director Andersen has provided some much-needed stability to CISA following a year of chaos and incompetent leadership,” said the panel’s top Democrat, Bennie Thompson of Mississippi.

9. [9]

   It is in the best interest of CISA’s mission to have an empowered leader who has earned the trust of the agency’s workforce and its stakeholders.” One industry source also said Andersen was a popular leader.

10. [10]

    With limited time remaining in this Congress, the administration would be wise to push his nomination through the Senate and put Nick on firmer footing.” Andersen has made a tangible difference at an agency that has seen dramatic budget and personnel cuts, said John Zangardi, a former chief information officer at DHS.

11. [11]

    … So morale has kind of gone back up, and I think Nick has been very instrumental in that.

12. [12]

    And I think he’s important in keeping that continuity going.” One of the notions of having a Senate-confirmed nominee is for the prospective leader to be well-vetted by an outside body.

13. [13]

    But having a Senate-confirmed nominee at the agency also helps CISA compete for its priorities within the interagency process and at the White House, Montgomery said.

14. [14]

    Absent that, keeping Andersen in the position in some capacity is the next-best option, he said.

15. [15]

    Montgomery also said Andersen has been making longer-term plans at the agency.

16. [16]

    Most recently, it released a strategy meant to carry CISA through 2030.

17. [17]

    Andersen “strikes me as someone who knows he’s got more than a month left in his job,” Montgomery said.

18. [18]

    “He’s thinking hard about it, and he’s starting to think three to six months out, which is a lot for this administration.” The post Could Nick Andersen’s leadership outlast the clock on his acting role?

19. [19]

    “We proudly support the work Acting CISA Director Nick Andersen has done in his role,” a DHS spokesperson said in response to questions about keeping Andersen on board and what became of that potential nominee.

20. [20]

    DHS referred CyberScoop to the White House for any further comment, but the White House didn’t respond to inquiries.

Read the original article →

What happened

Attackers posing as IT support on Microsoft Teams persuaded employees to grant remote control of their PCs. [1]

The attackers abused insecure Active Directory Certificate Services settings to obtain login certificates for privileged accounts, including a domain controller account. [2]

Why it matters

Microsoft reported investigating two intrusions of this type; the supplied text truncates the outcome of one investigation after stating that it resulted in a company. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Attackers posing as IT support on Microsoft Teams talked employees into giving them remote control of their PCs.

2. [2]

   They then used insecure Active Directory Certificate Services (AD CS) settings to obtain login certificates for privileged accounts, including one for a domain controller.

3. [3]

   Microsoft said in a report that it investigated two such intrusions, one of which resulted in company

Read the original article →

What happened

Chainalysis reported a cybersecurity incident that led to a data breach. [1]

The company said the incident was unrelated to the recent Binance hack. [2]

Chainalysis detected external attackers using “offensive agentic techniques” in October to gain access to its systems and internal tools. [3]

Known limitations

Based on evidence available at the time of the announcement, Chainalysis said it found no indication that the incidents resulted in unauthorized access to investigation … [4]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Blockchain analytics firm Chainalysis has suffered a cybersecurity incident that led to a data breach.

2. [2]

   According to the company’s Friday announcement, the incident is unrelated to the recent Binance hack.

3. [3]

   In October, the company detected external attackers using “offensive agentic techniques” to gain access to Chainalysis systems and internal tools.

4. [4]

   “Based on the evidence available to date, we have found no indication that these incidents resulted in the unauthorized access of investigation … More → The post Chainalysis breached using “offensive agentic techniques” appeared first on Help Net Security .

Read the original article →

What happened

The FBI attributed the October 29 theft of roughly $6.3 billion from Binance to TraderTraitor, a North Korean operation linked to the Lazarus Group. [1] [2] [3]

Binance said the incident began when a DevOps engineer’s laptop was compromised, giving attackers access to a service container and enabling unauthorized withdrawal approvals. [4]

TRM Labs reported that most of the approximately $6.36 billion haul disappeared within about 20 minutes; Elliptic estimated the total at roughly $6.43 billion and said $2.85 billion had been frozen or seized. [5] [6]

The FBI said the hackers began swapping the stolen funds for Ethereum and expected movement through DeFi platforms and instant-swap services to make tracing harder. [7]

Why it matters

Binance said it had replenished about 95 percent of the stolen assets and resumed withdrawals, while the remaining tokens were harder to replace because of limited liquidity. [8] [9]

Binance recorded approximately $3.64 billion in net outflows after withdrawals resumed, which the company described as about 2.1 percent of its reported assets. [10] [11]

Known limitations

Investigators still face the task of tracking billions of dollars as the hackers attempt to move the funds beyond their reach. [12] [13]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   The FBI has blamed North Korean hackers for the record-breaking $6.3 billion theft from cryptocurrency exchange Binance, pointing the finger at the notorious Lazarus Group as the exchange scrambles to replace stolen funds and reassure customers.

2. [2]

   In an alert published Saturday, the agency attributed the October 29 attack to TraderTraitor, a North Korean hacking operation linked to Lazarus, which has made a lucrative career out of relieving crypto exchanges of their digital assets.

3. [3]

   The FBI's attribution comes days after Binance admitted that hackers had made off with roughly $6.3 billion in cryptocurrency.

4. [4]

   According to the exchange, the trouble started with a compromised DevOps engineer's laptop, which gave the intruders access to a service container and allowed them to authorize withdrawals they had no business making.

5. [5]

   Blockchain intelligence firms TRM Labs and Elliptic had linked the theft to North Korea, with TRM reporting that most of the $6.36 billion haul disappeared in about 20 minutes.

6. [6]

   Elliptic, which puts the total closer to $6.43 billion, says it has verified that $2.85 billion of the stolen assets have been frozen or seized.

7. [7]

   According to the FBI, the hackers have started swapping their loot for Ethereum, with investigators expecting them to move the funds through decentralized finance (DeFi) platforms and instant swap services to make the money harder to trace.

8. [8]

   Binance has since resumed customer withdrawals, which it suspended after the attack, and says it has now replenished about 95 percent of the stolen assets.

9. [9]

   The remaining tokens are proving harder to replace because of their limited liquidity.

10. [10]

    That hasn't stopped users from heading for the exits.

11. [11]

    Binance recorded approximately $3.64 billion in net outflows after withdrawals resumed, although the company said this represented only around 2.1 percent of its reported assets.

12. [12]

    Replacing the stolen cryptocurrency is one thing.

13. [13]

    Getting it back from North Korea is another, and investigators face the considerable task of tracking billions of dollars as the hackers attempt to move it beyond their reach.

Read the original article →

What happened

IBM said two critical Langflow flaws could let a remote attacker with no account bypass authentication or run arbitrary code. [1]

Langflow is an open-source tool for building AI agents and workflows, and its vulnerability reports go to IBM. [2]

The flaws affect every Langflow release from 1.0.0 through 1.12.8; version 1.13.0 is identified as the only fix. [3]

Known limitations

The supplied evidence truncates the statement about CISA's Known catalog, so its complete status is unknown. [4]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Two critical flaws in Langflow could let a remote attacker with no account bypass authentication or run arbitrary code, IBM said last week.

2. [2]

   Langflow is an open-source tool for building AI agents and workflows, and its vulnerability reports go to IBM.

3. [3]

   Every release from 1.0.0 through 1.12.8 has the flaws, and the only fix is version 1.13.0.

4. [4]

   Neither flaw is in CISA's Known

Read the original article →

What happened

Trezor warned that a Trezor Safe 5 sold by CryptoBilis, a reseller linked to recent Ledger wallet drains, may contain a hidden implant capable of stealing the owner’s recovery phrase. [1]

The warning applies to purchases from CryptoBilis from March 2026 onward, although the supplied text is truncated before stating the complete condition or response. [2]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   A Trezor Safe 5 sold by CryptoBilis, the reseller linked to the recent Ledger wallet drains, may contain a hidden implant that steals the owner’s recovery phrase, Trezor has warned.

2. [2]

   “If you bought a Trezor from CryptoBilis from March 2026 onwards and are using it … More → The post Trezor warns some of its wallets may hide a seed-stealing implant appeared first on Help Net Security .

Read the original article →

What happened

Grocery retailers in Belgium, Ireland, Luxembourg, and Sweden reported cyberattacks affecting commercial refrigeration, with some appliances reportedly set to temperatures as high as 50°C and resulting food wastage. [1]

In Belgium, about 40 Delhaize stores were affected after attackers reportedly switched refrigerators and freezers into defrost mode overnight; Delhaize said fresh and frozen product availability was temporarily limited. [2] [3] [4]

Reported impacts included discarded fresh and frozen food at Delhaize and at least 13 SuperValue stores in Ireland; six Coop locations in central Sweden also experienced refrigeration issues. [5] [6] [7]

ICA confirmed an incident affecting refrigeration and freezer systems at a small number of stores outside its central network; one affected store reported having no fresh or frozen produce and no restoration status. [8] [9] [10] [11]

Why it matters

Earlier attacks in France reportedly affected hundreds of stores across multiple chains, and at least some affected sites were running outdated firmware on Danfoss refrigeration controllers. [12] [13] [14]

Known limitations

The article says it remains unclear whether the latest European attacks used the same methods as the earlier disruption in France, and the companies contacted did not identify who was behind the intrusions. [15] [16]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   The cyberattacks on commercial refrigerators and freezers in Europe continue, as a slew of grocery stores in Belgium, Ireland, Luxembourg, and Sweden report widespread food wastage as a result of miscreants raising the temperatures to highs of 50ºC (122°F).

2. [2]

   In Belgium, around 40 Delhaize stores were affected after the attackers reportedly switched fridges and freezers into defrost mode overnight, between Sunday and Monday, resulting in stock issues.

3. [3]

   "We have to throw away all of our merchandise, and it's both heartbreaking and very complicated operationally." A Delhaize spokesperson said it took steps to ensure stores remain stocked, although fresh and frozen products are "temporarily somewhat limited." "On Monday, 2 November, we identified an IT incident affecting the refrigeration systems in several dozen of our stores," they said.

4. [4]

   "In the affected stores, the range of fresh and frozen products is temporarily somewhat limited.

5. [5]

   Diego Louwers, a Proxy Delhaize store manager in Overijse, near Brussels, told RTL Info that the consequences of the cyberattacks were "catastrophic," forcing the store to throw out the entirety of its fresh and frozen products.

6. [6]

   Coop stores are affected by similar attacks too, with six locations in central Sweden experiencing fridge-freezer issues, according to a company spokesperson.

7. [7]

   Likewise, at least 13 SuperValue stores in Ireland are also affected, with fresh and frozen food being thrown out, according to parent company Musgrave speaking to RTE.

8. [8]

   Simultaneously, similar issues have affected Swedish grocery chain ICA, which confirmed attacks on a "small number of stores." "We can confirm that we have been informed of an incident overnight affecting a small number of ICA stores operating outside ICA’s central network," a company spokesperson said.

9. [9]

   "The incident impacted the stores’ refrigeration and freezer systems.

10. [10]

    One store, ICA Nära in Böda on Öland, said via social media that it is open today but has no fresh or frozen produce to sell.

11. [11]

    "We have no status on when the refrigerators and freezers are expected to be up and running again." The store manager, Mats Olsson, told SVT that he arrived to work on Monday morning and was greeted by a puddle of water and freezers set to 55 degrees C – a tale echoed by other managers across the country.

12. [12]

    The news comes less than a month after various grocery chains in France resorted to discarding bucketfuls of produce after their appliances were remotely defrosted by cybercrooks.

13. [13]

    Carrefour, Coopérative U, Intermarché, Monoprix, and others were hit with cyberattacks in mid-October, and hundreds of stores across the chains were reportedly impacted.

14. [14]

    At least some of the affected stores were running outdated firmware on their Danfoss refrigeration controllers, and shortly after the attacks were confirmed, CERT-FR published an alert pertaining to numerous Danfoss AK-SM and AK-SC controller compromises.

15. [15]

    It remains unclear if the latest attacks across Europe used the same methods as those used for the disruption in France last month.

16. [16]

    None of the companies that spoke to The Register on Monday responded to questions about who was behind the intrusions.

Read the original article →

What happened

Three weeks after an attack affected refrigeration units in French supermarkets, similar cyberattacks reportedly hit shops in Belgium, Luxembourg and Sweden and again spoiled refrigerated food. [1] [2]

In Belgium, refrigeration units at retailers including Delhaize, Carrefour and Spar were affected. [2]

The attackers reportedly switched the units’ evaporators remotely to defrost mode, causing the fridges to warm up. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Three weeks after the attack that turned refrigeration units in French supermarkets into ovens overnight, similar cyberattacks have hit shops in other European countries and again caused refrigerated food to be spoiled.

2. [2]

   Belgium, Luxembourg and Sweden affected “[In Belgium,] fridges and freezers have been affected at Delhaize, Carrefour and Spar, among others.

3. [3]

   The attackers remotely switched the units’ evaporators to defrost mode, causing the fridges to warm up,” Belgian news agency Belga reported today.

Read the original article →

What happened

Cyberattacks compromised emergency-alert apps in Russia and Ukraine, sending the public fake messages about missile, nuclear, chemical, radiation and street-fight threats. [1] [2] [3]

Ukraine reported its Air Alert app was likely compromised first; Russia later confirmed that attackers had abused its Ministry of Emergency Situations mobile app to send false information. [4] [5] [6] [7]

Russia said it was patching the vulnerability and restoring normal operation; about 90 minutes later it reported the app functioning normally. [8]

Why it matters

Russia said the mobile-app attack did not compromise the national alert system: primary warnings continued through regional and municipal systems, SMS, television and radio, while the app was supplementary. [8] [9] [10]

Some warning text contained contextual clues that it might be fake, including Russian-language references to the Oreshnik missile in Ukraine and to the Ukrainian P1-Sun drone in Russia. [11] [12]

Known limitations

A Ukrainian parliamentary committee chair said the Ukraine incident was almost certainly part of Russia’s cyber war; Russia did not explicitly blame Ukraine for the attack on its app. [13] [14]

The Ukraine incident was reported around the time a six-day Kherson ceasefire officially ended, but the supplied evidence does not establish that the timing was causal. [15] [16]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Cyberattacks on both Russia’s and Ukraine’s emergency alert apps resulted in fake messages about missile and nuclear strikes broadcast to the public.

2. [2]

   Officials from both countries confirmed the attacks, which occurred at similar times, on Sunday evening.

3. [3]

   According to the messages sent to devices after the compromise of Ukraine's alert app, the fake warnings pertained to various threats, such as street fights in Kyiv, chemical attacks, and radiation hazards.

4. [4]

   According to public statements and messages sent via social media, Ukraine’s alert app was hit first, with the country’s Air Force quick to dispel nuclear fears.

5. [5]

   "The Air Alert app has likely been compromised," it said via Telegram at around 2100 UTC.

6. [6]

   Stay calm, follow our messages on our channel!" At around 0030 UTC on Monday, Russia's Ministry of Emergency Situations confirmed the country’s app had also been abused, with fake messages sent to citizens' devices.

7. [7]

   The Russian Ministry of Emergency Situations' mobile app has been subjected to a massive cyberattack, allowing attackers to send fake information to the public," it said, also via Telegram.

8. [8]

   "Work is currently underway to patch the vulnerability and restore normal operation." The ministry issued an update around 90 minutes later, saying the app was once again functioning normally, and pointing out that an attack on the app was not the same as a compromise of the state’s national alert system.

9. [9]

   "Citizens are alerted through primary channels: regional and municipal alert systems (sirens, loudspeakers), communication networks (SMS messaging), and television and radio broadcasts.

10. [10]

    The mobile app is merely an additional, supporting information service," it stated.

11. [11]

    Alerts about the threat of nuclear fallout from official government warning systems would normally lead to panic, however, one of the earliest messages sent to citizens was written in Russian and referenced the "Oreshnik" missile, which was an immediate signal that the message may not be genuine.

12. [12]

    Equivalent alerts sent to Russian citizens also warned of impending nuclear strikes "at all regions of Russia," referencing "P1-Sun," the name of a Ukrainian attack drone.

13. [13]

    Oleksander Merezhko, who chairs the Ukrainian parliament's foreign affairs committee and noted the suspicious Russian-language alert, told the BBC the attack was almost certainly part of Russia's cyber war.

14. [14]

    "It is possible and we are quite prepared for such possibilities." Russia has not explicitly blamed Ukraine for the attack on its app, and official sources say the app is running as normal.

15. [15]

    Ukraine's announcement of the alert app cyberattack came almost simultaneously with the official conclusion of a six-day ceasefire in Kherson.

16. [16]

    Russia did not agree to a proposed extension of the ceasefire, which officially ended at around 2100 UTC – around the same time Ukrainians began receiving fake warning messages.

Read the original article →

What happened

Cisco Talos found a Windows infostealer called VOLTA-AUTODOXER that sends stolen data to an AI model and asks it to rank victims’ assets by potential monetary value. [1] [2]

Why it matters

Cisco researcher Ryan Fetterman described the reported cybercrime approach as stealing broadly and using AI to identify the most valuable information. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   A new Windows infostealer sends the data it steals to an AI model and asks it to rank the victim’s assets by how much money they could bring in, Cisco Talos has found.

2. [2]

   The malware calls itself VOLTA-AUTODOXER and turned up through Talos’ CAIRN … More → The post AI-powered infostealer picks out the most profitable parts of your stolen data appeared first on Help Net Security .

3. [3]

   “There is a new idea in the cybercrime world — cast a wide net, steal everything, and let AI sort out the specifics,” said Ryan Fetterman, a security researcher at Cisco.

Read the original article →

What happened

Google led a late-October takedown that caused a botnet of more than 1.3 million Android devices, mostly TV set-top boxes, to lose control of its servers. [1]

Google says it is highly confident that device maker Videostrong intentionally installed a backdoor in the boxes and sold access to criminals. [2]

Why it matters

The devices were used for ad fraud and to route other people's internet traffic through owners' homes. [3]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   A botnet of more than 1.3 million Android devices, mostly TV set-top boxes, lost control of its servers in late October in a takedown led by Google.

2. [2]

   Google says it is highly confident that device maker Videostrong intentionally put a backdoor in the boxes and sold access to criminals.

3. [3]

   They used the boxes for ad fraud and to pass other people's internet traffic through owners' home

Read the original article →

What happened

LLMJacking involves criminals hijacking corporate LLM access and tokens to consume AI services and computing resources, producing fraudulent charges that can exceed $100,000 per day; some organizations reportedly accumulated $1 million before access was revoked. [1] [2] [3]

Reported incidents included about 200,000 API requests in two minutes and more than 500,000 calls in under eight hours using stolen keys. [4] [5]

UNC6993 reportedly obtained LLM API access, generated additional keys, enabled cloud services, and incurred $100,000 in charges; another documented operation used premium models, high-volume inference, short-lived service accounts, and billing monitoring to bypass rate limits and track costs. [6] [7] [8]

A reported access method used a fraudulent session-hijacking page to induce users to submit an active-token JSON payload, allowing the operators to bypass password and multifactor-authentication controls. [9] [10]

Why it matters

Google reported a division of labor between actors establishing initial access to compromised cloud or AI services and downstream “LLM Mixers” managing monetization infrastructure. [11]

Google predicts criminals will increasingly prioritize LLMJacking over other resource-theft activity such as cryptojacking. [12]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Victim organizations are losing millions of dollars in token charges as criminals hijack their corporate LLM access to steal expensive computing resources and AI services.

2. [2]

   These fraudulent charges from resource consumption can exceed $100,000 a day, according to a Monday report by Google's Mandiant incident responders, who saw cumulative charges at some organizations hit $1 million before the victim companies revoked intruders' access.

3. [3]

   “Locking down these resources will not only protect organizations from runaway costs, but also protect the broader community from a deluge of cheap, autonomous attacks.” This tactic of hijacking access to LLMs is called LLMJacking, and it’s been increasing steadily over the past two years.

4. [4]

   In one extreme case, documented in an August report from CrowdStrike, a token thief sent about 200,000 API requests in just two minutes.

5. [5]

   In yet another incident, an intruder executed more than 500,000 LLM API calls in less than eight hours using stolen third-party API keys to power a token routing service called Jet Night, according to a Monday report from Google.

6. [6]

   In one case detailed in the report, a group Google tracks as UNC6993 illicitly gained access to LLM API keys, then generated additional keys and enabled services within the victim’s cloud projects, racking up $100,000 in charges.

7. [7]

   The threat intel biz also documented a different token thief subscribing victim accounts to Pay-As-You-Go agreements to access advanced models on the victim company’s dime.

8. [8]

   The crook selected premium foundation models, launched high-volume inference streams, and used a “burn and rotate strategy” to bypass rate limits by creating and deleting short-lived service accounts while auditing the billing interface to monitor financial impact.

9. [9]

   The crooks also spun up a session hijacking page purporting to be an application portal to join a group of LLM users.

10. [10]

    “This page tricks users into navigating to the legitimate LLM service website, and pasting their raw JSON payload containing an active access token, which was then posted to the backend API to bypass password and multifactor authentication (MFA) controls,” the report says.

11. [11]

    “For example, Jet Night offers an unlimited token plan for approximately $60 USD per month with alleged access to frontier models, a consumer service level that would typically run between $100 and $250 per month.” Jet Night has also admitted to multiple outages on its public Telegram channel, which the Google threat hunters note is “likely due to stolen keys being revoked as victims discover their respective compromises.” Specialized LLMjacking roles As more criminals join the LLMJacking ecosystem, Google says it has documented a division of labor between the criminals that establish initial access to compromised cloud and AI services, and those that manage downstream monetization infrastructure, called “LLM Mixers.” In one case that Mandiant responded to in mid-2026, UNC6993 compromised a cloud instance through a misconfigured Service Account key and used this access to grant further access to a model API.

12. [12]

    Google predicts miscreants will “increasingly prioritize LLMJacking” compared to other types of resource theft like cryptojacking.

Read the original article →

What happened

Trigger.dev reported unauthorized access to environment variables across a subset of organizations in a security incident; it has not publicly identified the affected organizations. [1] [2]

Trigger said the exploit used for access had been blocked and that affected customers had been notified of steps to prevent further security problems. [3]

Why it matters

If exposed environment variables contained sensitive credentials, an attacker could potentially access connected services and digital infrastructure or interfere with customer services and workflows. [4] [5]

Trigger supports durable AI agents and workflows, including retries, elastic scaling, and concurrent operations; the article says these capabilities could compound consequences depending on what exposed credentials permit. [6] [7]

Trigger’s webhook integrations include Stripe, Supabase, and Slack, potentially expanding the integrations affected if their credentials were exposed. [8]

Known limitations

Trigger provided little explanation, declined to give additional information, and directed readers to await a full incident report. [1] [9] [10]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   Trigger offered little explanation in its Sunday security incident report, noting that its investigation had identified “exposure across a subset of organizations” and that an attacker had gained unauthorized access to environment variables belonging to those organizations.

2. [2]

   Trigger has not publicly identified which organizations were affected by the intrusion.

3. [3]

   Whatever exploit was used to gain access has been blocked, the company added, and affected customers have been notified of steps they need to take to prevent further security problems.

4. [4]

   If compromised environment variables contain sensitive credentials, an attacker could basically end up with the keys to the kingdom, potentially gaining access to connected services and digital infrastructure.

5. [5]

   An attacker with stolen credentials could potentially interfere with a customer's connected services or workflows.

6. [6]

   For those unfamiliar with Trigger.dev, it’s a platform for building AI agents and workflows in TypeScript, but here’s the kicker: Trigger advertises itself as a durable execution platform that handles pesky things like retries, scaling, and keeping long-running tasks going through crashes and redeployments, while providing tools to monitor what those tasks are doing.

7. [7]

   Elastic scaling, automated retries, and, as Trigger notes, the ability to run lots of concurrent operations without timeouts could compound the consequences of compromised API keys, depending on what those credentials allow an attacker to access.

8. [8]

   Additionally, Trigger recently added webhooks to its offering, supporting services like Stripe, Supabase, and Slack, potentially expanding the range of integrations that could be affected if their credentials were exposed.

9. [9]

   We reached out to Trigger, which declined to provide any additional information on the incident.

10. [10]

    A company spokesperson instead told us to wait for a full incident report to learn more.

Read the original article →

What happened

A coalition working with Japan’s National Police Agency disrupted XCPE, a backdoor used in a botnet comprising more than 1.3 million Android devices across more than 200 countries. [1]

Google assessed with high confidence that Videostrong Technology intentionally developed, deployed, and operated XCPE and the botnet for financial gain. [2]

Google said Videostrong embedded XCPE in firmware and sold criminal affiliates access to install additional malware modules on devices shipped to customers. [3] [4]

TrendAI documented more than 3.8 million distinct home and mobile IP addresses connected to the operation between June 3 and October 1. [8]

The coalition disrupted command-and-control domains used to manage affiliate modules; GTIG assessed this could sever access to at least 10 million additional compromised devices because affiliates had other distribution channels. [9] [10]

Google said it cut ties with Videostrong and banned the OEM from making devices with preloaded Google apps. [11]

Why it matters

When affected devices joined home networks, operators could use customers’ internet connections to create proxy networks and conceal malicious traffic without their knowledge. [5]

The management agent connected to an MQTT server that gave operators full remote control to install or remove apps, change settings, and push updates. [6] [7]

Cited source evidence

These excerpts support the numbered claims above. They come from one source article and do not establish independent corroboration.

1. [1]

   A coalition of private-sector security firms working with Japan’s National Police Agency has disrupted XCPE, a backdoor used to build a massive botnet comprising more than 1.3 million Android devices across more than 200 countries.

2. [2]

   “We assess with high confidence that the backdoor and botnet were intentionally developed, deployed, and operated for financial gain by Videostrong Technology,” the Google Threat Intelligence Group (GTIG) said in a Monday blog.

3. [3]

   It builds Android devices, including home TV boxes and projectors.

4. [4]

   According to Google, Videostrong deliberately embedded the XCPE backdoor in device firmware and sold access to criminal affiliates, allowing them to install additional malware modules on devices shipped to unsuspecting customers.

5. [5]

   When buyers connected these devices to their home networks, the preinstalled backdoor allowed operators to create proxy networks and hide malicious traffic using the customers' internet connections without their knowledge.

6. [6]

   The firmware’s pre-installed management agent purported to be a standard remote-management client, according to TrendAI.

7. [7]

   It pulled updates from a GitHub page, and connected to a Message Queuing Telemetry Transport (MQTT) server that gave the operator full remote control of each box, allowing them to install and remove apps, change settings, and push updates to the infected devices.

8. [8]

   Between June 3 and October 1, TrendAI documented more than 3.8 million distinct home and mobile IP addresses connected to the operation.

9. [9]

   The coalition also disrupted the command-and-control domains used to manage the affiliate modules.

10. [10]

    “Because these affiliates each have diversified distribution channels for their modules beyond XCPE, we assess that taking down their C2 domains will sever access to at least 10 million additional compromised devices,” according to GTIG.

11. [11]

    Google said it had since cut ties with Videostrong, and banned the OEM from making devices with preloaded Google apps.

Read the original article →