pwn.watch: Supply chain updates

[critical] eMudhra intermediate CA private keys compromised

Fri, 23 Oct 2026 11:12:55 GMT

Eight eMudhra Global TLS intermediate CA private keys were found to be cryptographically weak / recoverable (researcher report Oct 18). Mozilla, Chrome, Apple and Microsoft blocked the intermediates; eMudhra revoked them Oct 19 and the ECC root was distrusted as a precaution. Downstream runtimes that ship their own trust stores (Go, Node.js, Electron, Python certifi, curl, etc.) needed emergency CA-bundle updates so they stop trusting the compromised chains.

Status: live · Patch: partial · Fixed in: Electron 44.9.1 / 43.8.1 / 42.11.16, Go 1.27.3 / 1.26.10, Node.js 22.23.4 / 24.22.1 / 26.12.1, Python certifi 2026.10.19, NSS 3.131.1, Java 27.0.1.0.2 / 25.0.5.0.2 / 21.0.13.0.2 / 17.0.21.0.2 / 11.0.33.0.2 / 8u511+ (CVE-2026-91403), Deno 2.9.8, rustls-webpki 0.103.16 / webpki-roots 1.0.10, pip 26.2.2 / uv 0.13.4 / sigstore 4.5.1 / conda 26.9.4 / pixi 0.82.1 (Python ecosystem), Ubuntu/Debian/Alpine/Fedora/Arch ca-certificates updates (see tracker), Docker Desktop 4.96.2, mitmproxy 12.3.0, LibreSSL 4.2.3 / 4.3.4 / 4.4.0

Latest updates:

2026-10-22: Tracker lists patched releases across distros, language runtimes and tools; Bun, Erlang certifi and Bottlerocket still pending. mitmproxy 12.3.0 drops eMudhra CAs. (source)
2026-10-22: eMudhra says a flaw in its April 30 2025 key generation ceremony produced a second set of weak keys, and those were the ones published to root stores; root cause still under investigation, replacement certs being issued to customers. (source)
2026-10-22: Internet Freedom Foundation says it has written to eMudhra, India’s Controller of Certifying Authorities and CERT-In asking for a fix. (source)

CVEs: CVE-2026-111943, CVE-2026-91403

[high] GhostAction returns: hijacked GitHub accounts push secret-stealing 'security audit' workflows to 30k+ repos

Fri, 23 Oct 2026 11:12:55 GMT

GhostAction, a campaign first documented by GitGuardian in Sept 2025, came back in 2026. It hit 772 repos in Aug-Sep 2026, then surged on Oct 8-12: about 1,900 compromised GitHub accounts pushed fake 'security audit' workflows to 30,000+ repositories (GitGuardian). The new payload exfiltrates the repo's Actions secrets plus every credential found in the full git history to 193.32.204.199 over plain HTTP. GitHub began preventing the workflow from running around Oct 9. The operator moved on to GitHub-themed phishing (my-github.com) and a VS Code tasks.json + fake .woff2 font stealer found in 94 repos.

Status: live · Patch: partial

Latest updates:

2026-10-16: OpenSourceMalware finds a second stage in 94 repos: VS Code tasks.json autoruns a stealer hidden in a fake Font Awesome .woff2 and installs a 5-minute cron. (source)
2026-10-13: GitGuardian update: Oct 8-12 wave targeted 30,000+ repos across ~3,000 users/orgs from ~1,900 compromised accounts; 3,174 secrets targeted. (source)
2026-10-11: Phishing kit on my-github.com steals password + 2FA and silently authorizes an OAuth app with repo/workflow scopes. (source)

[medium] GoDaddy mass-revokes 404,607 TLS certificates over CP/CPS profile mismatch

Fri, 23 Oct 2026 11:12:55 GMT

GoDaddy (Starfield) found that 404,607 TLS certificates carried policy information (policy OIDs, CPS URI) that didn't match its own published CP/CPS, which under the CA/Browser Forum Baseline Requirements means they must be revoked within five days. GoDaddy missed the Oct 18 deadline and says the certificates were revoked on Oct 21 2026. Nothing was hacked and no keys leaked, but sites still serving a revoked certificate can show browser warnings or become unreachable until the re-issued certificate is installed.

Status: live · Patch: partial · Fixed in: Re-issued certificates from the GoDaddy SSL dashboard (customer must install them)

Latest updates:

2026-10-21: GoDaddy's customer notice says the incorrectly issued certificates were revoked; affected sites must install the re-issued certificate. (source)
2026-10-19: 227,422 of 404,607 certificates revoked as of 05:29 UTC. (source)
2026-10-18: Five-day revocation deadline (23:45 UTC) passes with 170,566 certificates revoked; GoDaddy files a delayed-revocation incident. (source)

[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise

Fri, 23 Oct 2026 11:12:55 GMT

On Oct 21 2026 attackers compromised LiteLLM’s release pipeline and published malicious litellm==1.107.0 to PyPI (live ~2 hours) plus compromised Docker Hub/GHCR tags (v1.107.0, latest, main-latest, main-stable). The wheels install cook.pth / cook.py / sitecustomize.py that steal cloud, developer and AI-tool credentials at every Python startup and open a remote-code loader. Second LiteLLM compromise of 2026.

Status: live · Patch: patched · Fixed in: 1.106.2 (pin; last known safe). Malicious 1.107.0 removed from PyPI, Docker Hub and GHCR

Latest updates:

2026-10-23: SecurityWeek: the malicious 1.107.0 packages were online for roughly three hours and are estimated to have been downloaded over 49,000 times; enterprise customers pulling from LiteLLM’s private repository were not affected. (source)
2026-10-22: LiteLLM root cause: attacker held three developer GitHub CLI tokens, likely scraped from logs of an internet-exposed internal LiteLLM deployment (Claude Code can echo a gh OAuth token into logged response bodies), disabled branch protection and ran the release workflow against lookalike repo Berri-AI/litellm. (source)
2026-10-22: StepSecurity full teardown: payload exfiltrates to lookalike www.litellm.dev (registered Oct 13) and an hourly loader polls a GitHub dead drop (letters9813/pythonclient-test, now deleted). Infected hosts keep polling, so anyone re-registering that username could run code on them: kill the process holding /tmp/remote_code_loader.lock, delete cook.pth/cook.py/sitecustomize.py, pin 1.106.2 and rotate everything. (source)

CVEs: MAL-2026-2144

[critical] tensorlake@0.5.144 npm Shai-Hulud worm with hostage GitHub token

Fri, 23 Oct 2026 11:12:55 GMT

On Oct 8 2026, tensorlake@0.5.144 was published from the real GitHub repo (with npm provenance) carrying a preinstall hook that installs a Shai-Hulud-style credential-stealing worm. It harvests npm/GitHub/cloud/SSH/AI-tool secrets, spreads to other packages, and installs a “gh-token-monitor” that wipes the home directory if the stolen GitHub token is revoked. Pin 0.5.143; remove the monitor before rotating tokens.

Status: live · Patch: partial · Fixed in: 0.5.143 (safe pin); remove 0.5.144

Latest updates:

2026-10-08: 0.5.144 published via the project’s release workflow.
2026-10-08+: StepSecurity / Socket detections and public write-ups; remediation guidance emphasizes removing gh-token-monitor before revoke.
2026-10-07: Malicious commits land on tensorlakeai/tensorlake main.

CVEs: GHSA-8g63-53c9-65j2

[critical] SubQuery @subql/common 5.8.3 published with credential stealer + backdoor

Thu, 22 Oct 2026 10:04:00 GMT

On Oct 5 2026 @subql/common 5.8.3 was published to npm through SubQuery's own GitHub Actions trusted publisher, after a short-lived branch changed the release step to swap the built package for a tarball downloaded from ci-artifacts.dev. The payload ran on install (postinstall) and on import, stole CI/cloud/GitHub/npm/Kubernetes/Vault/SSH and AI-tool credentials, offered a reverse shell, and with a workflow-scoped token tried to push a secret-dumping workflow. It was live about 50 minutes; 5.8.2 is the safe version. Many @subql packages accept 5.8.3 through their version ranges.

Status: closed · Patch: patched · Fixed in: @subql/common 5.8.2 (npm 'latest')

Latest updates:

2026-10-10: SubQuery maintainer: compromised token deleted, security review started. (source)
2026-10-06: GMO Flatt Security publishes payload analysis and response guidance. (source)
2026-10-05T11:56Z: Malicious @subql/common 5.8.3 published via the repo's GitHub Actions trusted publisher (canary 5.8.3-onf-rt1 published ~32 min earlier). (source)

CVEs: GHSA-9333-3c4x-x3h5, MAL-2026-17571

[critical] OVHcloud CLI releases backdoored on GitHub

Tue, 20 Oct 2026 00:00:00 GMT

In mid-October 2026 OVHcloud said attackers hijacked a developer GitHub account and planted an information stealer in five releases of its open-source CLI. Users who installed those releases should treat workstations as compromised and rotate credentials.

Status: closed · Patch: patched · Fixed in: Clean releases after incident; reinstall from verified source

[high] TeamUpdraft / UpdraftCentral keys stolen; WordPress sites backdoored

Tue, 20 Oct 2026 00:00:00 GMT

UK plugin maker TeamUpdraft said attackers breached its website, stole UpdraftCentral connection keys, and used them to backdoor WordPress sites running UpdraftPlus/UpdraftCentral.

Status: closed · Patch: partial

[critical] AOMEI Backupper update servers backdoored (Mandiant)

Fri, 16 Oct 2026 00:00:00 GMT

Google Mandiant and ManageEngine reported that a threat actor tampered with AOMEI Backupper update servers mid-2026, pushing a backdoor to users across multiple countries. Disclosure clustered around Oct 16 2026.

Status: closed · Patch: patched · Fixed in: Vendor-clean updates after remediation

[critical] Rank Math PRO WordPress plugin download backdoored

Fri, 16 Oct 2026 00:00:00 GMT

SEO plugin vendor Rank Math confirmed attackers tampered with PRO version 3.0.123 on the official download site, planting hidden backdoors during an ~11-hour window. Sites that installed that build should audit and rebuild.

Status: closed · Patch: patched · Fixed in: Clean PRO builds after incident

[critical] CHAINDROP / Mini Shai-Hulud npm worm (keyv + 400+ packages)

Sat, 15 Aug 2026 00:00:00 GMT

In early August 2026 a Mini Shai-Hulud / CHAINDROP worm compromised keyv and related cache packages, then self-propagated via stolen npm tokens to 400+ packages (1B+ monthly downloads across the graph). Payload runs via preinstall (disabled by default on npm 12+), steals npm/GitHub/cloud/CI secrets, and republishes backdoored versions. Microsoft, Elastic, JFrog and Wiz published analyses.

Status: closed · Patch: partial · Fixed in: Pin known-good versions; purge caches; npm CLI 12+ disables preinstall by default

Latest updates:

2026-08-04: keyv/cacheable malicious releases observed; worm begins propagating.
2026-08-04/06: Microsoft, Elastic, JFrog publish analyses; 400+ packages listed.

[critical] Mini Shai-Hulud hits AntV / timeago.js npm ecosystem

Mon, 01 Jun 2026 00:00:00 GMT

May 2026 wave of Mini Shai-Hulud compromised packages across Alibaba’s AntV visualization ecosystem and timeago.js (via npm account atool). Payload harvested CI secrets from GitHub Actions runner memory and dumped credentials to public GitHub repos. StepSecurity documented the ongoing spread.

Status: closed · Patch: partial · Fixed in: Remove malicious versions; rotate CI/cloud secrets; pin clean releases

[high] OpenAI employee devices hit via TanStack Mini Shai-Hulud wave

Sun, 31 May 2026 00:00:00 GMT

In May 2026 OpenAI confirmed two employee devices were breached as part of the broader TanStack Mini Shai-Hulud npm supply-chain campaign. OpenAI said customer data, production systems, IP and deployed software were not impacted.

Status: closed · Patch: patched

[high] Nx Nx Console: Nx Console Embedded Malicious Code Vulnerability

Wed, 27 May 2026 00:00:00 GMT

Nx Console contains an embedded malicious code vulnerability that allowed a malicious version of Nx Console to be published. The compromised extension fetched an obfuscated payload that could harvested credentials from multiple sources on disk and in memory. Added to CISA KEV on 2026-05-27.

Status: closed · Patch: patched · Fixed in: See vendor advisory linked in sources

Latest updates:

2026-05-27: CISA added CVE-2026-48027 to the KEV catalog (due 2026-06-10).

CVEs: CVE-2026-48027

[critical] TeamPCP supply-chain campaign: Trivy → Checkmarx GitHub Actions

Tue, 31 Mar 2026 00:00:00 GMT

Threat actors tracked as TeamPCP compromised Trivy releases and GitHub Actions (including trivy-action / setup-trivy), then expanded into Checkmarx AST and KICS Actions and related artifacts. Malware stole CI/CD credentials (exfil as tpcp.tar.gz). Microsoft, Sysdig, CSA Singapore and Checkmarx published guidance in March 2026.

Status: closed · Patch: patched · Fixed in: trivy-action >= v0.35.0, setup-trivy >= v0.2.6, Checkmarx AST/KICS patched releases per Checkmarx updates

Latest updates:

2026-03: Trivy compromise disclosed; Microsoft guidance published.
2026-03: Campaign expands to Checkmarx GitHub Actions (Sysdig / Checkmarx updates).

[critical] ASUS Live Update: Live Update Embedded Malicious Code Vulnerability

Wed, 17 Dec 2025 00:00:00 GMT

ASUS Live Update contains an embedded malicious code vulnerability client were distributed with unauthorized modifications introduced through a supply chain compromise. The modified builds could cause devices meeting specific targeting conditions to perform unintended actions. The impacted product could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization. Added to CISA KEV on 2025-12-17.

Status: closed · Patch: patched · Fixed in: See vendor advisory linked in sources

Latest updates:

2025-12-17: CISA added CVE-2025-59374 to the KEV catalog (due 2026-01-07).

CVEs: CVE-2025-59374

[critical] Shai-Hulud 2.0: worm backdoors ~800 npm packages incl. Zapier, PostHog, Postman, ENS

Wed, 26 Nov 2025 00:00:00 GMT

A second wave of the Shai-Hulud worm ran in npm preinstall scripts (setup_bun.js), stole credentials with TruffleHog and pushed them to public GitHub repos, then republished packages with any npm tokens it found. Datadog counted 796 backdoored packages with 20M+ weekly downloads; Wiz saw 25,000+ attacker repos.

Status: closed · Patch: patched · Fixed in: Malicious versions unpublished; use versions published after 2025-11-24 per each vendor

Latest updates:

2025-11-26: GitHub privatizes malicious repos; public count drops to ~300 (source)
2025-11-26: PostHog publishes its post-mortem (source)
2025-11-24: First compromised package published (03:10 UTC) (source)

[high] GlassWorm: self-spreading VS Code / OpenVSX extension worm hidden in invisible Unicode

Fri, 31 Oct 2025 00:00:00 GMT

Koi Security found extensions on OpenVSX (and one on Microsoft's marketplace) carrying JavaScript hidden in invisible Unicode variation selectors. The malware stole npm, GitHub, Git and OpenVSX credentials to infect more extensions, went after crypto wallets, and set up SOCKS proxies and hidden VNC.

Status: closed · Patch: patched · Fixed in: Malicious releases removed from the marketplaces

Latest updates:

2025-10-20: Wider coverage; Microsoft marketplace extension also affected (source)
2025-10-17: Koi Security discloses GlassWorm on OpenVSX (source)

[critical] Shai-Hulud: first self-replicating npm worm hits 500+ packages incl. @ctrl/tinycolor and CrowdStrike

Tue, 23 Sep 2025 00:00:00 GMT

A worm spread through npm by stealing maintainers' npm and GitHub tokens with TruffleHog, then republishing their packages with a malicious bundle.js postinstall. It created shai-hulud GitHub workflows to exfiltrate secrets and made private repos public. CISA counted more than 500 affected packages, including @ctrl/tinycolor and several @crowdstrike packages.

Status: closed · Patch: patched · Fixed in: Malicious versions removed from npm; upgrade to versions published after the incident

Latest updates:

2025-09-23: CISA alert: widespread supply chain compromise impacting npm (500+ packages) (source)
2025-09-16: Largest burst, nearly 100 packages, including @crowdstrike scope (source)
2025-09-15: Worm discovered; @ctrl/tinycolor and ~40 packages found compromised (source)

[critical] chalk, debug and 16 other npm packages (2B+ weekly downloads) hijacked via fake 2FA email

Mon, 15 Sep 2025 00:00:00 GMT

Maintainer Josh Junon (qix) was phished by a fake npm 2FA-reset email from npmjs.help. The attacker published malicious versions of 18 packages, including chalk, debug, ansi-styles and strip-ansi, with code that hijacked crypto wallet transactions in browsers. They were live for about two hours.

Status: closed · Patch: patched · Fixed in: chalk 5.6.2, ansi-styles 6.2.3, strip-ansi 7.1.2, supports-color 10.2.2, ansi-regex 6.2.2, wrap-ansi 9.0.2, slice-ansi 7.1.2, has-ansi 6.0.2, chalk-template 1.1.2, supports-hyperlinks 4.1.2, debug and others: republished by the maintainer on 2025-09-13

Latest updates:

2025-09-15: Initial CVEs posted (source)
2025-09-13: All remaining affected packages republished by the maintainer (source)
2025-09-08: Malicious versions start appearing on npm (13:16 UTC) (source)

[critical] s1ngularity: malicious Nx releases used AI CLIs to hunt secrets, 5,500+ private repos exposed

Fri, 29 Aug 2025 00:00:00 GMT

Attackers abused a GitHub Actions injection bug in nrwl/nx to steal its npm token and published malicious nx and @nx/* versions for about four hours. The postinstall script used local AI CLIs (Claude, Gemini, Q) to find secrets and pushed them to public s1ngularity-repository repos. A second phase used stolen GitHub tokens to make 5,500+ private repos public.

Status: closed · Patch: patched · Fixed in: Malicious versions removed from npm (see GHSA-cxm3-wv7p-598c)

Latest updates:

2025-08-28/29: Second phase: 5,500+ private repos of 400+ users/orgs made public with stolen tokens (source)
2025-08-27: GitHub disables attacker-created s1ngularity repositories (09:00 UTC) (source)
2025-08-26: Malicious nx 21.5.0 and others published; npm removes them and revokes tokens that evening (source)

[high] eslint-config-prettier and friends hijacked via npnjs.com phishing (CVE-2025-54313)

Tue, 22 Jul 2025 00:00:00 GMT

A maintainer was phished through the typosquat domain npnjs.com. The attacker published malicious eslint-config-prettier versions whose install script ran node-gyp.dll on Windows, dropping the Scavenger infostealer. eslint-plugin-prettier, synckit, @pkgr/core, napi-postinstall and later the 'is' package were also hit.

Status: closed · Patch: patched · Fixed in: Malicious versions removed; use other eslint-config-prettier versions (see CVE record)

Latest updates:

2025-07-22: Malicious 'is' package versions found in the same campaign (source)
2025-07-18: Malicious eslint-config-prettier versions published after maintainer phishing (source)

CVEs: CVE-2025-54313

[high] reviewdog action-setup GitHub Action: reviewdog/action-setup GitHub Action Embedded Malicious Code Vulnerability

Mon, 24 Mar 2025 00:00:00 GMT

reviewdog action-setup GitHub Action contains an embedded malicious code vulnerability that dumps exposed secrets to Github Actions Workflow Logs. Added to CISA KEV on 2025-03-24.

Status: closed · Patch: patched · Fixed in: See vendor advisory linked in sources

Latest updates:

2025-03-24: CISA added CVE-2025-30154 to the KEV catalog (due 2025-04-14).

CVEs: CVE-2025-30154

[critical] tj-actions/changed-files compromised: CI secrets dumped in 23,000+ repos' logs

Thu, 20 Mar 2025 00:00:00 GMT

Attackers repointed the version tags of the popular tj-actions/changed-files GitHub Action to a commit that dumped runner memory, printing CI/CD secrets into workflow logs. It started with the compromise of reviewdog/action-setup and was aimed at Coinbase's agentkit repo first. Over 23,000 repositories used the action.

Status: closed · Patch: patched · Fixed in: 46.0.1 (see GitHub advisory GHSA-mw4p-6x4p-x5m5)

Latest updates:

2025-03-20: tj-actions and reviewdog maintainers finish remediation (source)
2025-03-18: CISA adds CVE-2025-30066 to KEV; reviewdog actions found compromised too
2025-03-15: GitHub removes the action, then restores a cleaned repository (source)

CVEs: CVE-2025-30066

[high] Ultralytics PyPI releases backdoored with a crypto miner

Wed, 11 Dec 2024 00:00:00 GMT

Attackers compromised the Ultralytics YOLO project's GitHub Actions workflows (by poisoning the Actions cache) and published ultralytics 8.3.41 and 8.3.42 to PyPI with an XMRig cryptominer. They later pushed 8.3.45 and 8.3.46 using a leftover PyPI API token. All four versions were removed. PyPI's analysis credits Trusted Publishing attestations with making the attack auditable.

Status: closed · Patch: patched · Fixed in: Malicious versions removed from PyPI; see vendor advisory for the clean release

Latest updates:

2024-12-11: PyPI publishes its analysis: 8.3.41, 8.3.42, 8.3.45 and 8.3.46 affected and removed (source)
2024-12-05: Issue #18027: published 8.3.41 wheel differs from GitHub and runs an XMRig miner (source)

[high] @solana/web3.js npm package backdoored to steal private keys

Wed, 04 Dec 2024 00:00:00 GMT

A publish-access account for @solana/web3.js was compromised. Malicious versions 1.95.6 and 1.95.7, live on npm from 15:20 to 20:25 UTC on 2024-12-03, exfiltrated private key material from apps and bots that handle keys directly. Non-custodial wallets were generally not affected. Fixed in 1.95.8.

Status: closed · Patch: patched · Fixed in: 1.95.8

Latest updates:

2024-12-04: GitHub advisory GHSA-jcxm-7wvp-g6p5 published; upgrade to 1.95.8 (source)
2024-12-03: Malicious 1.95.6 and 1.95.7 published to npm (15:20-20:25 UTC), then unpublished (source)

CVEs: CVE-2024-54134

[high] @lottiefiles/lottie-player npm package hijacked with a crypto wallet drainer

Thu, 31 Oct 2024 00:00:00 GMT

A LottieFiles developer's npm access was abused to publish @lottiefiles/lottie-player 2.0.5, 2.0.6 and 2.0.7 on 2024-10-30. Sites loading the 'latest' build from CDNs like unpkg and jsDelivr showed a wallet-connect popup that tried to drain visitors' crypto wallets. LottieFiles unpublished the versions and released 2.0.8, a copy of 2.0.4.

Status: closed · Patch: patched · Fixed in: 2.0.8

Latest updates:

2024-10-30: Malicious 2.0.5, 2.0.6 and 2.0.7 pushed to npm; users report a wallet popup (source)
2024-10-30: LottieFiles removes the compromised access, unpublishes the versions and publishes 2.0.8 (source)

[high] polyfill.io CDN turned malicious on 100k+ sites

Thu, 27 Jun 2024 00:00:00 GMT

The polyfill.io domain and GitHub account were bought in February 2024 by a Chinese company. The CDN, embedded via cdn.polyfill.io on more than 100,000 sites, then served malicious JavaScript that redirected some mobile visitors to a sports betting site. Sansec exposed it on 2024-06-25. Cloudflare began rewriting polyfill.io links to its own mirror, and Namecheap put the domain on hold.

Status: closed · Patch: patched · Fixed in: Remove polyfill.io references or switch to the Cloudflare/Fastly mirrors

Latest updates:

2024-06-27: Cloudflare rewrites cdn.polyfill.io to its mirror; Namecheap puts the domain on hold (source)
2024-06-25: Sansec reports the polyfill.io supply-chain attack hitting 100k+ sites (source)

[high] Justice AV Solutions (JAVS) Viewer Installer Embedded Malicious Code

Wed, 29 May 2024 00:00:00 GMT

Justice AV Solutions (JAVS) Viewer installer contains a malicious version of ffmpeg.exe, named fffmpeg.exe (SHA256: 421a4ad2615941b177b6ec4ab5e239c14e62af2ab07c6df1741e2a62223223c4). When run, this creates a backdoor connection to a malicious C2 server. Added to the CISA KEV catalog on 2024-05-29.

Status: closed · Patch: patched · Fixed in: See vendor advisory linked in sources

Latest updates:

2024-05-29: CISA added CVE-2024-4978 to the KEV catalog (federal deadline 2024-06-19) (source)
2024-05-23: CVE-2024-4978 published (source)

CVEs: CVE-2024-4978

[critical] xz-utils backdoor (CVE-2024-3094)

Wed, 29 May 2024 00:00:00 GMT

A maintainer persona, 'Jia Tan', slipped a backdoor into the release tarballs of XZ Utils 5.6.0 and 5.6.1. Through liblzma it targeted OpenSSH's sshd on distributions that link sshd against libsystemd, so a key holder could get unauthenticated remote code execution. Andres Freund spotted it after noticing SSH logins using a lot of CPU on Debian sid. It reached only bleeding-edge distributions such as Fedora 41/Rawhide and Debian unstable before it was caught.

Status: closed · Patch: patched · Fixed in: Downgrade to an uncompromised version such as 5.4.6 Stable (CISA), 5.6.2 clean release (2024-05-29, tukaani.org)

Latest updates:

2024-05-29: Lasse Collin publishes review notes 1.0 and new clean XZ Utils releases (source)
2024-04-09: XZ Git repositories available on GitHub again (source)
2024-03-30: xz@tukaani.org stops forwarding to Jia Tan (source)

CVEs: CVE-2024-3094

[critical] Ledger Connect Kit npm package hijacked to drain crypto wallets

Thu, 14 Dec 2023 00:00:00 GMT

Attackers phished a former Ledger employee's npm account and published malicious @ledgerhq/connect-kit versions 1.1.5 to 1.1.7. Because many dApps load it from a CDN without pinning a version, their users were shown wallet-drainer prompts. Ledger shipped a clean 1.1.8 within about 40 minutes of finding out.

Status: closed · Patch: patched · Fixed in: 1.1.8

Latest updates:

2023-12-14: Malicious connect-kit versions published to npm via a phished ex-employee account; Ledger ships 1.1.8 and the npm versions are removed (source)

[medium] PyPI pauses new users and projects amid a flood of malware

Sun, 21 May 2023 00:00:00 GMT

PyPI temporarily stopped new user registrations and new project names for about a day because malicious users and packages outpaced what its small admin team could handle.

Status: closed · Patch: no-fix-needed

Latest updates:

2023-05-21: Registrations resume (source)
2023-05-20: PyPI suspends new user and new project registration (source)

[critical] 3CX DesktopApp supply-chain attack (trojanized signed builds)

Thu, 20 Apr 2023 00:00:00 GMT

Signed 3CX DesktopApp builds for Windows and macOS shipped with embedded malicious code. Mandiant traced it to a North Korea-linked actor (UNC4736) who first got in through a trojanized X_TRADER install from Trading Technologies: a supply-chain attack caused by another supply-chain attack.

Status: closed · Patch: patched · Fixed in: See vendor advisory

Latest updates:

2023-04-20: Mandiant: the 3CX breach began with a trojanized X_TRADER package, the first software supply-chain attack it had seen caused by another (source)
2023-03-30: 3CX confirms the compromise and tells customers to uninstall the Electron desktop app (source)
2023-03-29: CrowdStrike reports malicious activity from the signed 3CXDesktopApp on customer machines (source)

CVEs: CVE-2023-29059

[medium] GitHub's RSA SSH host key briefly exposed in a public repo

Fri, 24 Mar 2023 00:00:00 GMT

GitHub's private RSA SSH host key for github.com was briefly exposed in a public repository. GitHub rotated it as a precaution, which meant anyone connecting over SSH with RSA saw a host key mismatch warning until they updated known_hosts.

Status: closed · Patch: patched

Latest updates:

2023-03-24: GitHub replaces its RSA SSH host key; users must update known_hosts (source)