[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fUeOtSE4JMU9702r9cXDc8HFiJ_spjyR1GR1SMYLXS94":3},{"article":4,"iocs":43},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"full_text":11,"url":12,"image_url":13,"published_at":14,"ingested_at":15,"relevance_score":16,"entities":17,"category_id":23,"category":24,"article_tags":27},"19401efb-43cf-4f82-bd3a-6874f475e3d1","Novo Nordisk Breach Exposes Software Development Pipeline Risk","novo-nordisk-breach-exposes-software-development-pipeline-risk-ec7acd","A leaked GitHub token underscores what most organizations get wrong: Treating secrets management as a tooling problem rather than an identity problem.","Novo Nordisk experienced a data breach stemming from a leaked GitHub token, exposing risks within their software development pipeline. The incident emphasizes that effective secrets management is fundamentally an identity problem, not merely a technical tooling issue.","Novo Nordisk breach highlights secrets management failures in software development.",null,"https:\u002F\u002Fwww.darkreading.com\u002Fcyber-risk\u002Fnovo-nordisk-breach-exposes-dev-pipeline-risk","https:\u002F\u002Feu-images.contentstack.com\u002Fv3\u002Fassets\u002Fblt6d90778a997de1cd\u002Fblta7151b99725c6823\u002F6a342d9a0da29c8273ce5feb\u002Fnovonordisk_gguy_shutterstock.jpg?width=720&quality=80&disable=upscale","2026-06-18T20:05:47+00:00","2026-06-18T22:00:16.899985+00:00",7,[18,21],{"name":19,"type":20},"GitHub","vendor",{"name":22,"type":20},"Novo Nordisk","26b0b636-0e31-4db1-bffb-61bdf9f20a58",{"id":23,"icon":11,"name":25,"slug":26},"Supply Chain","supply-chain",[28,33,38],{"category":29},{"id":30,"icon":11,"name":31,"slug":32},"2c8f44d4-b56e-47cf-9677-04f22c9ee78d","Identity & Access","identity-access",{"category":34},{"id":35,"icon":11,"name":36,"slug":37},"2e06f76c-d5b9-4f54-9eef-4d3447b10730","Breaches","breaches",{"category":39},{"id":40,"icon":11,"name":41,"slug":42},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[]]