The Morning Dev

Only the news worth knowing

‹
 
  • AAPL 344.17 ▼ 1.53%
  • MSFT 535.93 ▼ 3.58%
  • NVDA 181.60 ▼ 9.26%
  • GOOGL 282.57 ▼ 2.20%
  • AMZN 260.21 ▼ 2.19%
  • META 605.08 ▼ 3.96%
  • TSLA 343.69 ▼ 10.77%
  • AVGO 291.53 ▼ 10.43%
  • TSM 353.10 ▼ 10.78%
  • ORCL 115.16 ▼ 6.93%
  • AMD 404.40 ▼ 17.26%
  • NFLX 65.56 ▼ 1.25%
  • CRM 222.41 ▼ 2.07%
  • ADBE 246.44 ▼ 0.82%
  • INTC 52.25 ▼ 10.33%
  • IBM 247.11 ▼ 2.84%
  • PLTR 154.99 ▼ 9.73%
  • SNOW 269.54 ▼ 7.25%
  • NET 244.51 ▼ 8.28%
  • SAP 243.53 ▲ 1.45%

Tutorial

Your .env Is Not a Secrets Manager, and Your AI Tools Can Read It Too

DEV Community: python · By Lycore Development ·

Update, October 31, 2026: This month gave the post a real-world example. At least nine AI developer platforms disclosed breaches in October, and the attackers were specifically hunting stored environment variables, especially AI API keys, which they then validated and resold. One…

The Brief

  • The post argues that .env files are not a secrets manager and recommends a setup small teams can maintain.
  • An October 31, 2026 update says at least nine AI developer platforms disclosed breaches in October.
  • According to the update, attackers specifically sought stored environment variables, especially AI API keys, validated them and resold them.

Why it matters

Plaintext environment variables, including AI API keys, are a realistic target for attackers, and AI tools that read local files can expose them too.

Who’s affected

  • Developers and small teams storing API keys in .env files
  • Teams using AI developer platforms
  • #secrets-management
  • #env-files
  • #api-keys
  • #security
  • #ai-tools

Timeline

  1. Post updated with an example of October breaches at AI developer platforms

  2. DEV Community: python

    Your .env Is Not a Secrets Manager, and Your AI Tools Can Read It Too

How do you feel about this?

0 Comments

    More in Languages