securitylab_nJuly 17, 2026🇷🇺Translated from Russian

Cyberattack on Nichirei Logistics Group Disrupts Frozen Food Deliveries to KFC Japan and Thousands of Restaurants Nationwide

A cyberattack targeting Nichirei Logistics Group, Japan's largest operator of refrigerated and frozen logistics, quickly moved beyond computer systems and reached restaurant kitchens across the country. The incident disrupted deliveries to approximately 5,000 clients and caused immediate shortages of essential ingredients, most notably chicken for KFC Japan.

Nichirei Logistics Group reported a major system failure on July 13. Investigators later determined that attackers had gained access to the company's servers. To contain the intrusion and protect client information, Nichirei disconnected key systems, effectively halting large portions of its logistics network that relies on 140 refrigerated distribution centers.

The shutdown prevented normal warehouse operations and the dispatch of frozen and chilled products. During the investigation, the company discovered that personal data was stored on some of the affected servers. Nichirei notified Japan's data protection authority and stated it would publicly disclose any confirmed data theft once the review is complete.

The company has not revealed the identity of the attackers, the method used to breach its systems, or whether ransomware was deployed, citing security concerns. Technical details of the incident have also been withheld.

Clients dependent on Nichirei's infrastructure felt the effects almost immediately. KFC Japan confirmed that supplies to all of its more than 1,300 restaurants were disrupted, including chicken required for its signature Original Recipe. Some locations may reduce menu options or operating hours, and temporary closures remain possible if stocks run out. The chain also suspended online and mobile app orders because timely deliveries could not be guaranteed.

Other major operators reported similar problems. The ready-meal chain Hotto Motto, restaurant operator Yayoi Ken, and sushi chain Kura Sushi all experienced delivery interruptions. Supermarket chain Aeon faced product shortages in some stores, while frozen-food manufacturer TableMark was unable to ship goods to retail and corporate customers.

Nichirei expects to begin phased restoration of services on July 17, although no timeline has been provided for a complete return to normal operations.

Related articles

BoletimSecSupply Chain & Open Source

Supply Chain Attack Targets Arch Linux Community Repository

Arch Linux has temporarily suspended package adoptions in the Arch User Repository after detecting accounts taking over abandoned projects to insert malicious code. The platform later expanded the restriction by blocking all new submissions to the AUR to contain ongoing supply chain attacks. Attackers were adopting packages without active maintainers and introducing harmful changes through subsequent commits that could bypass user scrutiny due to established project history. Newly created packages containing malicious build commands, including requests for elevated privileges, were also discovered. Affected accounts have been banned and identified projects removed from the repository. The incident does not impact official Arch Linux repositories, with risk limited to community-maintained AUR packages that require manual review of PKGBUILD files before installation or updates.

HabrSupply Chain & Open Source

Malicious npm Packages Deploy Multi-Stage Trojan with Embedded GitLab Keys

Positive Technologies researchers uncovered a campaign in which an attacker published multiple trojanized packages to the npm registry under the accounts alex05255, mdrafiqulislamrabby, b.w1001, abdev8773 and mollspotwood54400. The affected packages include svg-fetcher, tradepilot, polytrade, polymarket-kit, react-svg-chunk, gamified-trading-system, font-huge, font-hub, mdb-vite, router-processor and route-processor. Each package concatenates several constants to build a C2 URL, downloads the next stage identified as token versions 106, 107, 108 and 116, and sends the hardcoded value logo in the bearrtoken header. Later stages contain heavily obfuscated JavaScript that collects username, hostname and operating-system information before establishing a WebSocket channel for command execution. Releases 106 and 116 also embed a public-private key pair belonging to a private GitLab instance operated by the threat actor, suggesting the use of CI/CD pipelines for code obfuscation and stage generation. The findings highlight the continued risk of supply-chain attacks through popular open-source repositories and the value of automated package monitoring.

HabrSupply Chain & Open Source

How to Audit All Python Virtual Environments for Compromised Packages Without Executing Python

The article describes a practical workflow for discovering whether any Python virtual environments contain known malicious package versions. The author maintains a registry of all .venv directories across local disks and external volumes using find commands and shell hooks. A Bash script then iterates through the registry and runs uv pip freeze against each environment to list installed dependencies without invoking the Python interpreter. This approach avoids risks highlighted by recent supply-chain attacks on packages such as LiteLLM, where even python -V or pip freeze could trigger malicious .pth files. The method also supports locating outdated packages, identifying usage of deprecated libraries, and searching project code for specific functions. Configuration settings like PIP_REQUIRE_VIRTUALENV=true and the uv tool further prevent accidental global installations.

HispasecSupply Chain & Open Source

GitHub and PyPI Introduce Time-Based Defenses Against Supply Chain Attacks

GitHub and PyPI have activated new time-based barriers to slow down supply chain attacks. Dependabot now waits a default of 72 hours before proposing version updates, while PyPI rejects new files added to releases older than 14 days. The changes target non-security version updates and attempts to poison older stable releases. Security updates remain immediate, and the cooldown can be adjusted via dependabot.yml. The PyPI restriction, effective since July 8 2026, addresses risks from compromised tokens or CI/CD pipelines. Both platforms aim to give the community time to detect malicious packages before widespread adoption.