Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: supply-chain (144 articles)Clear

Typosquatted Arch Linux AUR package imitating yay runs attacker code as root at install time

A malicious Arch User Repository account uploaded typosquatted packages, including yyay, which imitates the popular yay helper, with an install scriptlet that runs arbitrary downloaded code as root at pacman install or upgrade time. The payload was pulled from a personal project on a Russian code-hosting site, and the attacker left the normal install functions empty while placing the malicious command outside them. A malware scanner flagged yyay with high confidence, and a maintainer confirmed the payloads, banned the account, and deleted its packages. The incident follows an earlier AUR malware wave in July that briefly halted uploads across the repository.

Check
Verify AUR package names carefully before installing, review PKGBUILD and install scriptlets for commands that fetch and run remote code, and avoid lookalikes of yay and paru.
Affected
Arch users who installed the typosquatted AUR package ran attacker-controlled code as root at install time, risking credential theft, backdoors, or rootkits.
Fix
Remove any suspicious AUR packages, inspect systems that installed them for root-level compromise, rebuild from a clean state if needed, and install only vetted AUR helpers.

Low-cost MediaTek Android phones ship with system-level malware turning them into residential proxy nodes

Bitdefender detailed Midnight Mimosa, a campaign in which low-cost Android phones built on MediaTek platforms ship with a preinstalled system component, com.android.system.lite, that runs with system privileges. It grants itself accessibility, notification, and SMS permissions, installs and removes apps silently, performs ad fraud through an invisible overlay, and turns devices into residential proxy relays and botnet nodes. It disables the Play Store while dropping payloads to evade Play Protect. Bitdefender also found 13 related Play Store apps, and most infections are in Mexico, France, and Italy. Because the component sits in the system partition, users cannot remove it without firmware-level intervention.

Check
Avoid low-cost MediaTek Android devices from untrusted brands for sensitive use, and treat preinstalled system apps like com.android.system.lite as uncleanable without firmware reflashing.
Affected
Affected phones carry a system-partition component that silently installs apps, commits ad fraud, and relays residential-proxy and botnet traffic, and it cannot be removed by uninstalling.
Fix
Source Android devices through trusted vendors, reflash or replace compromised firmware, monitor networks for residential-proxy traffic, and remove the 13 related Play Store apps Bitdefender identified.

Ledger confirms hardware implant in wallets sold through reseller CryptoBilis after cryptocurrency theft reports

Ledger confirmed that a hardware wallet sold through the reseller CryptoBilis contained an unauthorized hardware implant, following reports of stolen funds from buyers in Southeast Asia. A pseudonymous blockchain investigator put losses above 86 million dollars, while Ledger described a limited number of affected devices, all sold through that reseller. Ledger paused sales through CryptoBilis, which halted all hardware wallet sales pending the investigation. Ledger advised buyers from the past 90 days not to set up unconfigured devices, and to move assets to a new signer with a fresh seed if a device was already initialized. Users should avoid unauthorized resellers.

Check
If you bought a Ledger from CryptoBilis in the last 90 days, do not initialize unconfigured devices and move any existing assets to a new signer with a fresh seed.
Affected
Ledger hardware wallets bought through the reseller CryptoBilis may contain an implant that has been linked to cryptocurrency theft from buyers in Southeast Asia.
Fix
Buy hardware wallets only from authorized channels, never reuse a pre-printed recovery phrase, move funds to a new device and seed if compromise is possible, and never share recovery phrases.

Credential-stealing GitHub Actions workflows planted across tens of thousands of repositories via compromised maintainer accounts

Socket, StepSecurity, and GitGuardian reported a resurgence of the GhostAction supply chain campaign, in which more than 500 GitHub accounts committed a credential-stealing workflow to tens of thousands of repositories since October 7. The attacker likely used maintainer personal access tokens leaked in infostealer logs, starting with the author of the pyxel game engine and spreading to other accounts. The injected workflow, disguised as a security audit, scans the working tree and full git history against 13 secret patterns, including AWS, Anthropic, OpenAI, and GitLab keys, and exfiltrates them over plain HTTP to a hardcoded address. Earlier GhostAction activity hit 772 repositories and thousands of secrets.

Check
Search repositories and forks for security-audit.yml or github_actions_security.yml workflows added since August 31, and if present assume compromise and rotate every exposed secret.
Affected
Repositories whose maintainer tokens were leaked had a rogue workflow injected that steals GitHub Actions secrets and any credentials in the working tree and git history.
Fix
Revoke compromised GitHub credentials, delete the malicious workflow from all branches and forks, rotate all exposed secrets, and store tokens outside infostealer-reachable locations.

Compromised Tensorlake npm package spreads Shai-Hulud worm that steals developer credentials and republishes itself

Socket and StepSecurity reported that version 0.5.144 of the tensorlake npm package, a TypeScript SDK, was published with obfuscated malware tied to the Shai-Hulud supply chain attack. A preinstall hook launches a loader that runs a worm under the Bun runtime. It harvests npm, GitHub, AWS, Vault, Kubernetes, and SSH credentials, .env files, cryptocurrency wallets, and configuration for Claude, Cursor, and other tools, then enumerates the victim's other packages and republishes them with forged provenance to spread. A PowerShell monitor watches the stolen GitHub token and runs a destructive handler if the victim revokes it, so remove the package before rotating that token.

Check
Check whether any project installed tensorlake 0.5.144, remove it before revoking tokens to avoid the destructive handler, then rotate all exposed credentials and audit republished packages.
Affected
Developers who installed the compromised tensorlake version had npm, GitHub, cloud, and SSH credentials stolen, and the worm may have republished their own packages with forged provenance.
Fix
Remove the malicious package, rotate npm, GitHub, cloud, and SSH credentials, review published packages and GitHub Actions workflows for tampering, and follow Socket and StepSecurity guidance on token revocation order.

Eight malicious npm packages downloaded over 40,000 times deliver Overlord RAT and credential stealer

CloudSEK and Checkmarx detailed MALFEX, a campaign they attribute to a lone actor who has published eight malicious npm packages downloaded 40,767 times in total, with function-flag alone accounting for 37,419. The Windows-focused packages deliver three payloads: Overlord, an open-source Go remote access trojan that pulls its command-and-control address from Solana transactions; a Node.js stealer that targets Discord, browsers, Telegram, and cryptocurrency wallets; and a downloader. Lifecycle and postinstall hooks fetch and run remote executables, with one package saving a hidden node.exe to the AppData directory. Three packages, function-flag, function-color, and cdn-img-fetch, were still live on npm at publication.

Check
Audit npm dependencies for the named MALFEX packages, remove any that are present, and check Windows hosts for Overlord RAT activity and a hidden node.exe in the AppData directory.
Affected
Windows developers who installed the MALFEX packages, especially function-flag, may be infected with the Overlord remote access trojan or a stealer targeting browsers, Telegram, and wallets.
Fix
Remove the malicious packages, rebuild affected Windows systems, rotate credentials for browsers, Discord, Telegram, and wallets, and block the known payload download domains.

Bitget says attacker used third party security product flaw to steal 388 million dollars

Cryptocurrency exchange Bitget said the attacker who stole about 388 million dollars gained access through a vulnerability in a third-party security product the exchange used. The attacker exploited the flaw to obtain high-level internal credentials, then on September 24 used them to reach an internal management system and insert fraudulent withdrawal commands into wallet backend services, where they were treated as legitimate. The stolen funds came from Bitget's hot and warm wallets, while its offline cold wallets were unaffected. CEO Gracy Chen described the incident publicly, confirming the earlier statement that a critical wallet backend system had been compromised and used to spoof transaction data and trigger approvals.

Check
Review third-party security products in privileged positions for patch status and blast radius, and treat their credentials as high-value targets requiring isolation.
Affected
Organizations relying on a vulnerable third-party security product can have its high-level credentials stolen and abused to command core backend systems.
Fix
Inventory and patch third-party security tooling, scope its access tightly, add out-of-band approval for high-value transfers, and monitor for anomalous internal commands.

Popular Chrome ad blocker extensions disclose selling users' browsing data to third parties

LayerX research found dozens of Chrome extensions, reaching millions of users, that legally sell or share user data under terms accepted at install. Among ad blockers, it confirmed eight reserving the right to sell or share user information, together reaching over 5.5 million users. Stands AdBlocker, with three million users, sells browsing data for market analytics, and Poper Blocker, with two million users, discloses selling identifiers, browsing activity, and behavioral profiles inferred from visited URLs. Smaller ad blockers route browsing data and even AI conversations through data brokers. The finding shows tools installed to stop tracking can themselves become data exfiltration channels, a browser extension supply chain risk static malware scanning misses.

Check
Inventory browser extensions across managed fleets, remove data-selling ad blockers like the named ones, and enforce an allowlist for permitted extensions.
Affected
Users who installed these ad blockers consented in the terms to having their browsing data, identifiers, and inferred profiles sold or shared with third parties.
Fix
Deploy an enterprise extension allowlist, review extension permissions and privacy terms, and educate users that ad blockers can monetize their data.

Compromised GitHub Actions came back online still executing Mini Shai-Hulud credential malware

Socket reported that two GitHub Actions, actions-cool/issues-helper and actions-cool/maintain-one-comment, were disabled a second time after their repositories became accessible again on September 16, months after being compromised in the May Mini Shai-Hulud campaign. When the repositories returned, their release tags were not cleaned up and still pointed to the malicious content introduced on May 18, so any workflow referencing either action by a version tag resumed downloading and executing the payload on its next run. The original May 18 compromise ran code that harvested credentials from CI/CD pipelines and exfiltrated them, activity linked to the Mini Shai-Hulud cluster through a shared exfiltration domain. GitHub has again disabled both repositories.

Check
Audit workflows for references to the two actions-cool actions, pin actions to trusted commit hashes, and rotate any CI/CD secrets exposed since September 16.
Affected
Pipelines referencing the affected actions-cool actions by version tag re-ran the May 18 payload after September 16, harvesting and exfiltrating CI/CD credentials.
Fix
Remove or repin the actions to vetted commits, rotate pipeline secrets, and prefer commit-hash pinning over mutable version tags for third-party actions.

Attackers plant Go malware in HashiCorp Terraform registry in first such supply chain abuse

Aikido disclosed Go-based malware distributed through two Go modules and two Terraform providers, the first time attackers have used HashiCorp's centralized registry as a distribution vector. The flagged items include kreuzwenker/docker, with 1,449 downloads, and gocommunity-io/dockerd, alongside two Go modules. The malware overlaps with the Graphalgo campaign that ReversingLabs attributed to North Korean actors in February, in which developers are approached on LinkedIn, Facebook, or job forums by fake Web3 companies and asked to run a benign repository that pulls the malicious behavior from a dependency. The discovery coincides with a fresh batch of malicious npm and PyPI packages delivering the same threat, flagged by Checkmarx, JFrog, and SafeDep.

Check
Vet Terraform providers and Go modules by publisher and source, pin and review versions, and scan developer machines for the flagged packages and modules.
Affected
Developers pulling the malicious Terraform providers or Go modules, or the paired npm and PyPI packages, execute Go malware tied to the Graphalgo campaign.
Fix
Restrict registries to vetted providers, enforce allowlists for infrastructure-as-code sources, and treat unsolicited coding tasks from recruiters as supply chain risk.