Vendor

CrowdSec

2 mentions in 7 days · 3 in 30 days · 3 total · first seen Sep 1, 2026 · last 14h ago

Timeline3 articles

TanStack Supply Chain Attack Lets Hackers Steal 170 Private CrowdSec GitHub Repositories

Attackers used an OAuth token stolen in the TanStack npm supply chain attack to clone 170 private CrowdSec GitHub repositories, later leaked on a forum.

CrowdSec disclosed that attackers copied about 170 private GitHub repositories using the OAuth token of a former employee whose account was compromised in the TanStack npm supply chain attack (CVE-2026-45321). The compromise chained an unsafe pull_request_target workflow, GitHub Actions cache poisoning, and OIDC token extraction to publish 84 malicious releases across 42 @tanstack packages that harvested GitHub, npm, cloud, Kubernetes, Vault, and SSH credentials. The repositories were cloned from a Toronto IP on May 22 and the theft surfaced on September 16 when source code appeared on a cybercrime forum. Exposed data included emails of 83 users (<0.05% of 150,000), details on 51 potential investors, and an AWS SNS credential that was tested once.

Cyber Security NewsSep 19, 11:21 UTC · 14h agoData breach in the wild 2 sources CVE-2026-45321

CrowdSec Says TanStack npm Attack Led to Copy of 170 Private GitHub Repositories

CrowdSec says the TanStack npm supply chain attack let an attacker copy 170 private GitHub repos via a former employee's retained account.

On May 22 an attacker used a GitHub OAuth token from a former CrowdSec employee whose organization access had been kept active, copying about 170 private repositories containing the web console, data science models, and blocklist consensus algorithm. CrowdSec attributes the access to CVE-2026-45321, the May 11 publication of 84 malicious versions of 42 TanStack npm packages that stole GitHub tokens, SSH keys, and cloud credentials from developer machines. The leaked archive also exposed email addresses of 83 users and names, emails, and investment context of 51 potential investors from 2020. The same campaign affected Mistral AI and OpenAI, and the only usable credential found in the leak, an AWS SNS publish token, saw an attempted misuse on August 17.

The Hacker Newsupdated Sep 19, 11:21 UTC · 14h agofirst Sep 19, 07:14 UTC · 18h agoData breach in the wild 2 sources CVE-2026-45321

Bot detection arrives in CrowdSec 1.8.0, along with two DoS fixes

CrowdSec 1.8.0 adds WAF bot detection via challenges and fingerprinting and fixes denial-of-service flaws in HTTP and Kubernetes audit datasources.

CrowdSec 1.8.0, released August 31, introduces bot detection in its WAF using client challenges and fingerprinting, plus fixes for two denial-of-service vulnerabilities in the HTTP acquisition datasource (unbounded decompressed body size, trusted Content-Length) and the Kubernetes audit webhook datasource (unbounded request body reads). The release also adds a dedicated Kubernetes datasource pulling logs directly from the apiserver, new HTTP helpers for external queries in the expression language, and performance work on the decisions stream endpoint. The challenge requires SSE4.1 and writable-executable memory, so some legitimate visitors may be blocked.

Help Net SecuritySep 1, 00:00 UTC · 19d agoTools1

Related CVEsby mentions

CVE-2026-453219.62%
Supply chain compromise: credential-stealing code in 42 @tanstack/* npm packages
CVE-2026-45321 is a supply chain compromise in which 84 malicious versions across 42 @tanstack/* npm packages (including @tanstack/react-router, @tanstack/react-start, @tanstack/history, and related router/start packages) were published to the npm registry on 2026-05-11 between roughly 19:20 and 19:26 UTC, authenticated through TanStack's legitimate GitHub Actions OIDC trusted-publisher binding. The attacker chained three known weakness classes — a pull_request_target 'Pwn Request' misconfiguration, GitHub Actions cache poisoning across the fork-to-base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — allowing publication under a trusted identity without modifying the publish workflow. Each affected package received exactly two malicious versions carrying credential-stealing malware, so developers, CI pipelines, or downstream builds that installed them could have npm, GitHub, and cloud credentials extracted; related reporting (FBI, StepSecurity) links the campaign to stolen cloud credentials and a self-spreading 'Mini Shai-Hulud' worm that also hit packages in other ecosystems such as Mistral AI and Guardrails AI. Exposure is limited to consumers who installed the two malicious versions published per package during the exposure window; other users of these widely deployed libraries were not affected by the malicious publishes. Exploitation is confirmed in the wild: the issue was added to CISA's Known Exploited Vulnerabilities catalog on 2026-05-27 with known ransomware use, and EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile).
· tanstack @tanstack/arktype-adapter · tanstack @tanstack/eslint-plugin-router KEV ransomware PoC ×2large

Appears with

vendor TanStack 2 victim CrowdSec 2 vendor GitHub 2 organization CrowdSec 2 product GitHub OAuth token 1 product TanStack npm packages 1 product TanStack Router 1 product TanStack Start 1 vendor AWS 1 vendor Mistral AI 1 vendor npm 1 vendor OpenAI 1 victim Mistral AI 1 victim OpenAI 1 organization GitHub 1 product AWS SNS 1

Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.