/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

US investigators probing a breach at Codecov, a software auditing company, that affected some of its 29K customers; the breach was in Jan. but detected in April

Reuters Raphael Satter

Discussion

  • @ph1 Pete Hodgson on x
    Oh wow, this is a brutal vulnerability. Anyone using a certain method to upload code coverage numbers was also possibly sending any secrets in their CI env vars (quite likely direct access to prod) directly to hackers. https://about.codecov.io/...
  • @lizrice Liz Rice on x
    “it would have been easy for Codecov or any of its customers to detect the malice by [simply] checking the shasum. The ability for the malicious version to escape notice for three months indicates that no one bothered to perform this simple check” 😰 https://arstechnica.com/...
  • @flugazi @flugazi on x
    Codecov breach impacts GoDaddy, Atlassian, P&G etc. https://www.reuters.com/...
  • @ihadrami_ @ihadrami_ on x
    @Techmeme Gosh! It took them around three months to detect the breach, and I wonder if any of their clients was impacted seriously when the software was in circulation.