Security Roundup: Log4j Alert, Credential Leaks, Breaches and Sanctions

· Original article ↗

Summary

The roundup covers debate over a Log4j alert, exposed cloud credentials, mobile banking malware, data breaches and ransomware claims, a Russian cyber training program, and U.S. sanctions against Iranian cyber actors.

Key points

  • Log4j developers called a reported Log4j 2 remote-code-execution issue a “known security non-finding,” while acknowledging that exploitation may be possible under specific circumstances.
  • U.S. Bancorp said LockBit’s claims involved a potential incident at a fourth-party provider and that it had no evidence its own systems or data were compromised.
  • Truffle Security found more than 700 active corporate AWS keys among 10,616 exposed keys reviewed; Intruder also reported finding exposed repositories and active credentials.
  • Zimperium reported 30 mobile malware families targeting more than 800 banking and fintech apps across 44 EMEA countries, with attackers increasingly using AI in the attack chain.
  • Troy Hunt found that a large portion of data attributed to the alleged Carhartt breach was synthetic benchmark data, suggesting the claimed volume of real customer data was overstated.
  • Paylogix said attackers stole files containing sensitive personal and financial information; Akira claimed the attack. Manchester Airports Group reported customer data access but said airport operations and safety were unaffected.
  • The U.S. Treasury sanctioned Iranian cyber actors it accused of critical-infrastructure compromises and cyber theft.

Article Details

Event Type
Weekly cybersecurity news roundup covering vulnerability concerns, credential exposure research, data breaches, ransomware claims, company news, and government sanctions.
Impact
The reported incidents included exposure of sensitive personal and financial data, potentially active credentials that could provide access to cloud environments and private code, and ransomware-related data threats. U.S. Bancorp said it had no evidence its systems or data were compromised and attributed the claims involving its name to a potential incident at a fourth-party provider. Manchester Airports Group said airport operations, passenger safety, and aviation security were unaffected. The Log4j issue was described by its developers as a known security non-finding despite its potential for remote code execution under specific circumstances.

People

Threat Actors

Vendors

Products

Industries

Related Articles