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

Poisoned Adform ad script swapped crypto wallet addresses on customer sites

Attackers compromised a widely used tracking script from advertising firm Adform, turning it into a browser-side tool that rewrites cryptocurrency wallet addresses. The malicious code was appended in obfuscated form to Adform's trackpoint-async.js library, served from the company's own infrastructure, so any site loading it ran the altered script in visitors' browsers. It swapped Bitcoin, Ethereum, and Tron addresses both in the clipboard and in form fields, redirecting transfers to the attacker. Adform detected and removed the code on July 27 and says it did not install software or persist after a page closed, but cached copies may linger. It has not said how many page loads were affected.

Check
Warn people who sent cryptocurrency after visiting sites recently to clear their browser cache and verify every wallet address, and review whether your own sites embed third-party scripts that could be poisoned.
Affected
Anyone who copied or entered a crypto wallet address on a site loading Adform's tracking script on July 27; the swapped address silently redirected funds, and cached copies may still be active.
Fix
Limit and monitor third-party scripts, use subresource integrity where possible, isolate payment and wallet pages from ad and tracking code, and treat any shared external script as a single point of compromise.

Arch Linux halts package adoptions after infostealer floods the user repository

The Arch Linux project temporarily disabled adoption of packages in its user repository, the AUR, after a wave of malicious takeovers of existing packages. Attackers seized packages through compromised maintainer accounts or by adopting orphaned ones, then shipped a Rust-based infostealer that grabs browser credentials, cryptocurrency wallets, password manager data, cloud and developer secrets, AI service API keys, and SSH keys. It also opens remote command execution over an encrypted Tor channel and spreads to other machines using stolen SSH keys. A researcher tracking the campaign claims more than 200 packages were hit, including some popular ones, though that list is not independently confirmed.

Check
If you use the AUR, review recently installed or updated packages and their maintainers, inspect build files before installing, and rotate SSH keys and secrets if you ran a suspect package.
Affected
Arch Linux users who install from the AUR; a hijacked or adopted package can run a Rust infostealer that harvests developer, cloud, and AI credentials and SSH keys, then self-spreads.
Fix
Read AUR build scripts before installing, prefer well-maintained packages, rotate exposed credentials and SSH keys, watch for outbound Tor connections, and treat orphaned or newly adopted packages with particular caution.

Amazon ties the chalk and debug npm hijacks to North Korean hackers

Amazon's threat intelligence team linked several major npm supply chain attacks to a North Korean group tracked as Sapphire Sleet, also known as BlueNoroff. The group compromised the small typo-crypto package in March 2025 as a test, then hijacked the hugely popular debug and chalk packages in September 2025, and axios in March 2026. The debug and chalk incident, which pushed a wallet-draining script into packages with billions of weekly downloads, reached roughly one in ten cloud environments within two hours. The attackers gained access by phishing package maintainers through lookalike npm domains, then published malicious versions that auto-installing projects pulled in.

Check
Review whether your projects or CI pulled compromised versions of typo-crypto, debug, chalk, or axios during the affected periods, and check developer and build environments for wallet-draining or credential-stealing behavior.
Affected
Developers and organizations that auto-install npm dependencies; a phished maintainer account can push a malicious version of a hugely popular package that reaches thousands of downstream environments within hours.
Fix
Pin and verify dependencies, add a delay before adopting new versions, watch for maintainer-account phishing, protect publishing accounts with phishing-resistant MFA, and monitor build environments for credential and wallet theft.

Compromised joyfill npm packages run a remote access trojan when imported

Attackers published malicious versions of the @joyfill/components and @joyfill/layouts npm packages that run a remote access trojan as soon as the package is imported, not merely installed. Because the payload executes at import time, defenses that block install scripts, such as installing with scripts disabled, do not stop it. The malicious code sat only in the published tarballs with no matching source change, pointing to a registry or publishing pipeline compromise. Once loaded, it profiles the host, opens a remote-control channel, and can run shell commands, upload files, read the clipboard, and tamper with developer tools, using blockchain networks to resolve its next payload for resilience.

Check
Check whether any project, CI runner, or build imported the malicious @joyfill/components or @joyfill/layouts versions, focusing on import-time execution rather than only install scripts.
Affected
Developers and CI pipelines that imported the compromised joyfill packages; the trojan runs in any process that loads them, giving attackers remote control and access to developer credentials and tools.
Fix
Remove the malicious versions, pin known-good releases, rebuild from clean state, rotate secrets reachable from affected machines, and add runtime and egress monitoring, since install-script controls do not catch import-time payloads.

Security scanners can be turned into a foothold for supply chain attacks

New research shows that application security scanners embedded in the software pipeline can themselves be attacked, because analyzing a repository is not always a read-only action. Many scanners execute code or process files in ways that can be forced to run attacker content when it is handled without isolation. For example, a tool that scans cloud configuration files against a folder of custom rules can be fed a rule that is actually a malicious program, which the scanner runs when it loads it. Since scanners often hold broad access to source, secrets, and build systems, a compromised one is a strong pivot point into the wider environment.

Check
Review how your code and configuration scanners handle untrusted repository content, and check whether they execute rules, plugins, or files without sandboxing and multi-tenant isolation.
Affected
Teams whose security scanners process untrusted repository content without isolation; an attacker controlling a scanned repo can plant content that runs code inside the scanner, which often holds broad access to secrets.
Fix
Run scanners in isolated, least-privilege sandboxes, treat all scanned content as untrusted input, enforce multi-tenancy separation, and limit the source, secrets, and build access that scanning environments hold.

GitHub delays Dependabot version updates to keep poisoned packages out

GitHub is adding a default three-day cooldown before Dependabot opens pull requests for new package versions, aimed at supply chain attacks where a poisoned release spreads through automated updates before anyone catches it. Security updates that answer a known advisory still ship immediately; only routine version updates wait. GitHub points to the September 2025 compromise of chalk, debug, and other packages, whose crypto-stealing versions were live for roughly two hours, and notes its advisory database logged more than 6,500 npm malware advisories in the year to May 2026, around eighteen a day. Most malicious releases are caught within hours, so a short delay filters out the majority.

Check
If you use Dependabot, confirm the cooldown is enabled and consider tuning the window in dependabot.yml, and apply similar delay logic to any other automated dependency tooling you run.
Affected
Projects with automated dependency updates that pull new releases immediately; a poisoned version of a popular package can reach reviewers and installs during the short window before it is caught and yanked.
Fix
Adopt a cooldown on version updates while keeping security fixes immediate, pin and verify dependencies, review update pull requests rather than auto-merging, and monitor for advisories on packages you rely on.

Suno breach exposes 55 million accounts eight months after a developer was compromised

Data from a November 2025 breach at AI music platform Suno surfaced publicly in July, with Have I Been Pwned indexing 55,282,226 unique email addresses. Alongside the addresses, the corpus held names, phone numbers, physical addresses, and purchase records, plus tens of thousands of Stripe entries containing partial card data: card type, expiry date, and the last four digits. Reporting indicates the intrusion started with malware delivered through third-party code on a developer's machine, which yielded credentials for private repositories and internal databases. Suno has said no sensitive personal information was compromised and has not notified affected users.

Check
Suno users should check Have I Been Pwned, change the password there and anywhere it was reused, and be alert to phishing that references their account or past purchases.
Affected
Roughly 55 million Suno users whose email addresses, names, phone numbers, physical addresses, and purchase records were exposed, with partial card data for a subset; most have not been notified.
Fix
Use unique passwords and enable multi-factor authentication where offered. Organizations should treat developer workstations as high value targets, since third-party code running there can hand over repository and database access.

Hugging Face says an autonomous AI agent breached its production systems

Hugging Face, the largest public repository of AI models and datasets, disclosed an intrusion into its production infrastructure that it says was driven end to end by an autonomous AI agent system. The attacker used code execution paths in the dataset processing pipeline for initial access, then harvested credentials and reached internal clusters, though the company found no evidence that public models or datasets were tampered with. The campaign ran thousands of actions across short lived sandboxes, with self migrating command and control staged on public services. Hugging Face's own AI assisted anomaly detection flagged it, and it has rotated affected credentials and rebuilt compromised nodes.

Check
Users of Hugging Face should rotate access tokens and review recent account activity, and teams should check what credentials their model and dataset pipelines hold and how far those reach.
Affected
Organizations running AI model and dataset pipelines that execute untrusted content; Hugging Face's own dataset processing paths gave an autonomous agent initial access, credentials, and reach into internal clusters.
Fix
Rotate Hugging Face tokens, treat datasets and models as untrusted code rather than data, sandbox processing pipelines, limit credentials reachable from them, and tighten admission controls on clusters running that work.

Ernst and Young says client tax documents were stolen from a support platform

Ernst & Young is notifying clients of a breach at a third-party IT service management platform used by staff supporting its tax practice. Support tickets submitted through the platform could include attached documents containing client tax information, and the firm says an unauthorized third party accessed the platform between March 28 and April 12 and downloaded documents belonging to a number of clients. EY detected the activity on April 23, roughly two weeks after it stopped, and filed breach notifications with the California Attorney General in July. The exposed data includes personal and financial information used to prepare tax filings.

Check
EY tax clients should watch for a notification letter, monitor financial accounts and credit, and treat unexpected messages referencing their tax filings or the firm as likely phishing.
Affected
EY tax clients whose documents were attached to support tickets; personal and financial information used to prepare tax filings was downloaded, which supports identity theft and convincing targeted phishing.
Fix
Affected clients should consider a credit freeze and monitor accounts. Organizations should limit what sensitive data staff attach to helpdesk tickets, set retention limits on attachments, and assess vendor security.

SleeperGem backdoor skips build servers to plant persistence on developer machines

Researchers at StepSecurity documented SleeperGem, a supply chain attack in which malicious versions of three RubyGems packages were published over two days, including one impersonating Microsoft's Git Credential Manager. Each release is a loader that fetches a second stage from an attacker controlled server, then checks around thirty environment variables that continuous integration platforms set. If it finds any, it exits and does nothing; on a developer machine it drops a native daemon and installs persistence. The accounts behind the packages were ordinary ones that had gone dormant for years, which is what made them attractive to hijack, and the releases had no matching source repository tags.

Check
Check developer machines and lockfiles for the malicious gem versions published July 18 and 19, and look for unexpected daemons or persistence rather than relying on build system logs.
Affected
Developers who installed the malicious gem versions on their own machines; the loader deliberately skips continuous integration environments and instead drops a persistent native backdoor where credentials and source code live.
Fix
Remove the affected gem versions, rotate credentials on affected developer machines, treat dormant maintainer accounts and releases without matching source tags as risk signals, and monitor endpoints, not just pipelines.