---
title: "Discussion on \"The Attacker Didn't Break Into Production. It Walked In Through Development\" | Hashnode"
description: "Discussion on \"The Attacker Didn't Break Into Production. It Walked In Through Development\". Chainstack's breach started in a dev environment, reached production five days later, and stayed quiet — until the company said the honest thing about its customers' keys."
url: "https://hashnode.com/posts/the-attacker-didn-t-break-into-production-it-walked-in-through-development/6aead83c3ed9f2c028e09a58"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Attacker Didn't Break Into Production. It Walked In Through Development](https://nulltrace.hashnode.dev/the-attacker-didn-t-break-into-production-it-walked-in-through-development?utm_source=hashnode&utm_medium=feed)

Chainstack's breach started in a dev environment, reached production five days later, and stayed quiet — until the company said the honest thing about its customers' keys.

Nov 4 · 4 min read · nulltrace.hashnode.dev  
Read the article

-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#data-breach](https://hashnode.com/tag/data-breach)
-   [#blockchain](https://hashnode.com/tag/blockchain)
-   [#devsecops](https://hashnode.com/tag/devsecops)
-   [#supply-chain](https://hashnode.com/tag/supply-chain)

## Written by

[Cyber Knight](https://hashnode.com/@cyberknight2479)

@cyberknight2479

  
[View profile](https://hashnode.com/@cyberknight2479)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
