The Encryption Key Was in the API Response

There is a particular kind of security failure that reads like a horror story told by an accountant: South Korea's government-backed startup platform, Modu-ui Changup, stored its applicants' data encrypted. The algorithms were fine. The architecture was the problem. In July, investigators confirmed that the platform's encryption key was being served up inside API responses alongside the data it protected, and external crawlers simply collected both. About 5,000 successful applicants lost their email addresses, evaluation comments, and startup idea summaries. The data had been encrypted the entire time. It just came with the keys.

The detail that makes this worth your attention is how early the warning was. A month before the leak was confirmed, concerns were already raised that applicant information could be structured and exposed through API responses. The government said it acted immediately. It did not disclose whether anyone fixed the underlying architecture. Then an AI solutions company got involved in a way the ministry is still investigating, and on June 18 they announced the leak. Encrypted data with the key sitting next to it is not protected data; it's data with a delay.

Source article image
Source image 1

The operational lesson is blunt: encryption without key separation is theater. If your API can return ciphertext and the corresponding key in the same response envelope, you have built a decryption service for whoever crawls your endpoints. The fix list is unglamorous but non-negotiable — keys live in a KMS or secrets manager that applications request from on demand, never stored alongside data; API response

Source article image
Source image 2
s get audited for what they actually return, not what the spec says they return; and when a key does leak, you re-encrypt everything it touched, because rotating the key doesn't un-expose the data. The question worth asking of any system you've built or maintain: can your encryption keys leave the building through an endpoint you forgot to check?

Sources

  • BleepingComputer — South Korean startup platform breach exposes key management failures: bleepingcomputer.com
  • The Herald Business — Ministry of SMEs and Startups calls 'Modu-ui Changup' data breach a hacking incident: biz.heraldcorp.com
  • Kobaran — South Korea Data Breach Exposes Startup Applicants' Personal Data: kobaran.com

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more