Breach of the Day

Nichirei Logistics Group, Japan's largest refrigerated food transport company, confirmed this week that hackers breached its servers, according to The Record. The company disconnected critical systems to contain the damage, bringing parts of its nationwide logistics network to a halt.

The fallout was immediate and physical. KFC Japan, which relies on Nichirei's 140 refrigerated distribution centres, reported disruptions to deliveries of its signature Original Recipe chicken across all 1,300-plus restaurants. Online ordering was suspended. Bento chain Hotto Motto, sushi chain Kura Sushi, retail giant Aeon, and frozen food manufacturer TableMark all reported delays or outages of their own.

Nichirei has not confirmed whether ransomware was involved, and has withheld technical details about how the attackers gained access. The company did confirm that some affected servers contained personal data and has notified Japan's data protection authorities. Investigations are ongoing.

This is a textbook supply chain attack (where hackers target a supplier or logistics provider to cascade disruption across many companies at once). One breach, thousands of customers affected. Japan has seen a wave of similar incidents recently, including hits on telecoms giant KDDI and brewer Sapporo Holdings, though there is no confirmed link between them.

What you should do: If you are a business using a third-party logistics or infrastructure provider, ask them directly about their incident response plan and whether they carry cyber insurance. Knowing the answer before a crisis is considerably more useful than finding out during one.

Four packages in the @asyncapi namespace — a popular open-source toolkit used by software developers to build and document event-driven APIs (programming interfaces that let applications communicate) — were quietly poisoned and pushed to npm (Node Package Manager, a public library where developers download reusable code), according to The Hacker News.

The attacker did not steal any passwords or publishing tokens. Instead, they gained push access to the project's code repositories and used the projects' own legitimate automated release pipelines to publish the infected versions. The resulting packages carried valid, official-looking provenance certificates — digital stamps that are supposed to confirm a package was built by the project's authorised workflow. Those stamps were technically accurate. The workflow did build the packages. The commits that triggered it just were not legitimate.

Once a developer installed one of the affected packages and their application loaded the module, a hidden implant quietly fetched an encrypted second-stage payload called Miasma from IPFS (InterPlanetary File System, a decentralised peer-to-peer file storage network). Miasma is a full command-and-control framework that supports six separate communication channels, including HTTP, Ethereum smart contracts, and peer-to-peer mesh networks — making it unusually difficult to block.

Beyond credential theft and spreading to other machines on the local network, the malware sets up persistent autostart entries across Windows, macOS, and Linux. It also carries a dead man's switch: if a monitored token is revoked, the malware wipes its own directory. It avoids systems running CrowdStrike, SentinelOne, Microsoft Defender, CarbonBlack, Cylance, Osquery, Tanium, or Qualys, and skips machines with their language set to Russian.

All five malicious versions have been removed from npm. If you or your team installed any of the affected packages, treat that machine as compromised and audit it fully.

Nihon Kotsu, Japan's largest taxi and chauffeur operator, confirmed over the weekend that attackers broke into its internal systems, according to Bleeping Computer. The company operates 8,558 taxis and over 2,000 chauffeur vehicles, employs more than 18,000 people, and pulls in roughly $1 billion in annual revenue. It is, in short, not a small target.

The attackers got in through malware infection. Nihon Kotsu detected the intrusion and pulled the plug on affected systems to stop further spread — the digital equivalent of slamming every door shut and hoping the fire stays contained. As a result, the taxi dispatch system, web bookings, reservation management, and telephone services all went offline and remain unavailable.

One detail worth noting: the company's specialised taxi service for pregnant women approaching their due date is suspended across Tokyo and several surrounding cities. That is not an abstract inconvenience.

No ransomware group has claimed responsibility yet, and no confirmed data leak has been reported, though the company is actively investigating. External cybersecurity experts have been brought in.

If you use Nihon Kotsu services, the company recommends the GO taxi app as an alternative for now. More importantly: if you receive any email or message appearing to come from Nihon Kotsu, do not open attachments or click links. Attackers frequently impersonate victims immediately after a breach.

jscrambler is a developer tool used to obfuscate (scramble and hide) JavaScript source code, protecting it from being copied or reverse-engineered. It is installed as part of automated software build processes, which means it often runs with broad access to a machine's files and credentials.

On July 11, 2026, version 8.14.0 of the jscrambler npm (Node Package Manager — a registry where developers download and share code libraries) package was published with a hidden payload. The moment a developer or automated system ran the install command, a native binary silently dropped into the system's temp folder, marked itself executable, and launched in the background. No user interaction required. The whole thing was over before anyone knew it started.

Security firm Socket flagged the malicious release just six minutes after it went live, according to The Hacker News. That window was enough for real damage.

The payload is a Rust-built infostealer (a program designed to silently collect and transmit sensitive data) targeting exactly what developer machines hold: AWS, Azure, and Google Cloud credentials; cryptocurrency wallets including MetaMask and Exodus; the Bitwarden password manager vault; browser passwords and cookies; and session tokens for Discord, Slack, and Telegram. It also swept config files for AI coding tools including Cursor, VS Code, and Claude Desktop, where API keys tend to sit unguarded.

On Linux, the binary went further, loading an eBPF (extended Berkeley Packet Filter — a mechanism that runs code directly inside the Linux kernel) program from memory. That is a kernel-level foothold, not a standard file grab.

The malicious version was pushed directly to npm under a legitimate maintainer account, bypassing the normal GitHub release process entirely. Analysts at StepSecurity and SafeDep confirmed no matching commit exists in the public repository.

The package sees roughly 15,800 downloads per week. Anyone who installed 8.14.0 should assume their development machine's secrets were exfiltrated.

What to do: Check your package-lock.json or equivalent dependency file for jscrambler version 8.14.0. If it is present, treat the machine as compromised: rotate all cloud credentials, API keys, and tokens immediately. Downgrade to 8.13.0.

Progress Software has ordered customers running ShareFile's Storage Zone Controller offline, according to The Hacker News. The company says it is responding to a "credible external security threat" and has temporarily disabled access to affected accounts while working with outside security experts.

The Storage Zone Controller is a Windows server companies run on their own premises, letting files stay on internal storage while ShareFile's cloud handles sharing and access. It typically sits at the network's edge, reachable from the internet — which makes it useful and, as it turns out, a standing target.

The shutdown order rather than a patch tells you what you need to know. When a fix exists, companies issue it. Ordering servers fully offline usually means no fix exists yet.

Progress says it has found no evidence of unauthorised access to accounts or data. That is careful wording: it says nothing about what may have happened on the controllers themselves.

This is not the first time this software has been in the crosshairs. In 2023, when the product still belonged to Citrix, attackers exploited a critical unauthenticated flaw (CVE-2023-24489) in the same component, and CISA flagged it as actively exploited.

What to do:

• Keep affected controllers offline until Progress issues clear guidance.
• Confirm you are on version 5.12.4 or later on the 5.x line, or any 6.x release. This closes earlier known flaws but does not authorise a restart.
• If your controller was internet-facing, treat it as a potential incident. Preserve logs, check for unfamiliar files in web and storage folders, and begin your incident-response process.

A supply chain attack (where an attacker compromises a trusted software component that developers rely on, infecting everything built with it downstream) hit the Injective Labs SDK this month, according to Bleeping Computer.

The Injective SDK is a development toolkit that programmers use to build cryptocurrency wallets, trading bots, and decentralised finance applications on the Injective blockchain. It gets downloaded roughly 50,000 times a week.

An attacker compromised a legitimate contributor's GitHub account on June 8 and used it to publish a malicious version of the package — version 1.20.21 — on npm (Node Package Manager, the central repository where developers download code libraries). The same poisoned version was pushed across 17 related packages.

The malware did not fire on installation. Instead, it waited until a developer called wallet functions, then silently captured mnemonic seed phrases (a 12–24 word backup code that grants full wallet access) and private keys. Those credentials were bundled together, encoded, and sent to an attacker-controlled server disguised as normal traffic to Injective's own infrastructure.

The malicious package was downloaded 310 times before being deprecated. Critically, it was deprecated rather than removed — the poisoned files are still accessible.

If you or your team use the Injective SDK: check your dependency versions immediately, transfer any cryptocurrency held in affected wallets to fresh wallets with new keys, and rotate all credentials in your build environment.

Japan's second-largest mobile carrier, KDDI, has confirmed a breach affecting customers across five internet service providers, according to Bleeping Computer.

Attackers got into a shared email platform on May 16 by exploiting a zero-day vulnerability (a security flaw unknown to the software vendor at the time of attack) in third-party software. The intrusion went undetected for a month. KDDI discovered it on June 17.

The numbers: 12.2 million email addresses and 7.6 million passwords were exposed across current and former customers of STNet, JCOM, Chubu Telecommunications, NIFTY Corporation, and BIGLOBE. Some passwords were stored in hashed or encrypted form, which makes them harder to misuse. KDDI has not confirmed how many were stored in plaintext.

Attackers with your email address and password can try that same combination across dozens of other services. Think of it like someone copying a key to your front door and then testing it on every flat in your building.

KDDI has since deployed EDR (Endpoint Detection and Response) software to catch future intrusions and has mandated forced password resets through affected ISPs.

What to do: If you use any of these ISPs — or if you reuse passwords anywhere — change those passwords now. Use a password manager to generate unique ones for each account. Enable two-factor authentication on your email wherever possible.

Accenture, a global consulting and IT services firm that works with major corporations and governments worldwide, has confirmed it was breached after a hacker going by "888" began selling stolen data on a cybercrime forum, according to Bleeping Computer.

The threat actor claims to have taken just over 35 GB of data. The alleged haul includes source code, RSA keys (private encryption credentials), SSH keys (used to authenticate into servers remotely), Azure PAT tokens (personal access tokens that grant programmatic access to Microsoft Azure cloud services), storage access keys, and configuration files. As proof, the attacker shared a screenshot showing them cloning an internal Azure DevOps repository under an Accenture hostname.

Accenture confirmed the incident, saying the source had been remediated and that operations were unaffected. The company did not comment on what was actually taken, how the attackers got in, or whether any customer data was exposed.

This is not a first offence for either party. The same "888" actor previously tried to sell Accenture employee data after a third-party breach in 2024. The LockBit ransomware group also hit Accenture in 2021.

The real concern here is the type of data reportedly stolen. Source code and cloud access tokens are not just embarrassing to lose — they are keys to the kingdom. An attacker holding a company's Azure access keys can potentially reach anything that company stores or builds in the cloud.

What you should do: If your organisation uses Accenture-managed services or shared cloud environments, contact your account team to confirm whether your infrastructure was within scope of the affected systems.

A threat cluster tracked as UNK_MassTraction, believed to be aligned with Chinese state interests, has been running a targeted campaign against physics and engineering departments at U.S. and Canadian universities, according to The Hacker News. The campaign was first detected in May 2026 and singled out administrators and professors with ties to national security research, astrophysics, and particle physics.

The attackers exploited two critical flaws in Roundcube, an open-source webmail platform commonly used by universities. Both CVE-2024-42009 and CVE-2025-49113 had already been patched, but the targeted departments were still running vulnerable versions — suggesting the attackers did their homework first and identified targets before sending a single email.

The attack required no unusual action from victims. Opening the malicious email inside Roundcube was enough. A payload called IceCube executed silently in the browser, harvesting saved credentials, two-factor authentication (2FA) codes, and session cookies. Think of it like a thief who only needs you to open your front door — not even step outside.

From there, IceCube used the stolen session data to trigger a second, more severe remote code execution (RCE) flaw, allowing the attackers to run code directly on the mail server. The primary tool deployed was VShell, a known post-exploitation tool previously linked to a China-nexus cluster called UNC5174. A fallback web shell called SquareShell was also used when VShell deployment failed. An ELF loader called SNOWLIGHT helped deliver the tools and has appeared in other Chinese-attributed intrusions.

What you should do: If your organisation runs Roundcube, confirm it is updated to the latest version immediately. Any university IT team should audit mail server logs for unexpected outbound HTTP POST requests or access to unusual plugin endpoints.

Cloud security firm Sysdig has published findings on what it describes as the world's first ransomware campaign operated entirely by a large language model (LLM) — an AI system capable of understanding and generating human-like text, here repurposed as an attack engine. According to Sysdig's Threat Research Team, the campaign, named JadePuffer, required no skilled human operator.

The attack began by exploiting CVE-2025-3248, a known flaw in Langflow (an open-source tool used to build AI-powered applications). From there, the AI agent worked autonomously: it harvested credentials, mapped connected systems through lateral movement (moving through a network from one compromised machine to others), installed a persistence mechanism via a cron job (a scheduled task that runs automatically), and ultimately reached a production database server.

What happened next is striking. The agent encrypted 1,342 configuration items inside a Nacos service (a configuration management tool used in cloud environments) and deleted the originals. The encryption key was randomly generated and never saved anywhere. The victim cannot recover their data, even if they pay.

The AI narrated its own actions inside its payloads — which Sysdig notes is actually a new detection opportunity for defenders watching network traffic.

The real warning is the speed. The agent recovered from a failed login and produced a working fix in 31 seconds.

What you should do: Patch internet-facing systems immediately, especially anything running older or unmonitored software. Ensure production databases are not directly reachable from public-facing services. Check that credentials are rotated regularly and not stored in plaintext config files.