/
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

GitHub says an attacker used stolen OAuth user tokens issued to Heroku and Travis-CI to steal private repository data from dozens of organizations including npm

GitHub revealed today that an attacker is using stolen user tokens (issued to Heroku and Travis-CI OAuth) to download data from private repositories.Source:The GitHub BlogandHeroku Status.

BleepingComputer Sergiu Gatlan

Discussion

  • @githubsecurity @githubsecurity on x
    GitHub has uncovered evidence that an attacker abused stolen OAuth user tokens issued to two third-party OAuth integrators, Heroku and Travis-CI. Read more about the impact to GitHub, npm, and our users. https://github.blog/...
  • @malwarejake Jake Williams on x
    Not to ruin anyone's holiday weekend, but if your org uses @heroku or @travisci, there's an active investigation going on into compromised OAuth tokens used for integration with @GitHub (who initially identified the issue). Action this now. 1/2 https://status.heroku.com/... https…
  • @nikcharlebois @nikcharlebois on x
    Security alert: Attack campaign involving stolen OAuth user tokens issued to two third-party integrators https://github.blog/...
  • @campuscodi Catalin Cimpanu on x
    On April 12, GitHub Security began an investigation that uncovered evidence that an attacker abused stolen OAuth user tokens issued to two third-party OAuth integrators, Heroku and Travis-CI, to download data from dozens of organizations, including npm https://github.blog/...
  • @jot Jonathan Markwell on x
    The worst security incident in 14 years of using Heroku and GitHub strikes on one of the UK's best bank holiday weekends. Who else will be spending a chunk of this lovely day reviewing security logs and rotating access tokens? :( https://status.heroku.com/... https://github.blog/…
  • @rstephens Robert Stephens on x
    “To mitigate impact from potentially compromised Auth tokens, we will revoke over the next several hours all existing tokens from the Heroku GitHub integration.” Whoa. https://status.heroku.com/
  • @jacobian @jacobian on x
    If you run apps on Heroku you should be keeping an eye on this incident: https://status.heroku.com/... The GitHub breach disclosed earlier involved oauth tokens belonging to the Heroku Dashboard, so there's a very high likelihood that some part of Heroku got popped too.
  • @marypcbuk Mary Branscombe on x
    attacker abused stolen (but not stolen from GitHub) OAuth user tokens issued to two third-party OAuth integrators, Heroku and Travis-CI, to download data from private repos of dozens of organizations, including npm https://twitter.com/...
  • @quinnypig Corey Quinn on x
    Frankly, if you're still using @travisci then you've missed an escalatingly dire series of memos over the past few years. https://twitter.com/...