In our first post on credential harvesting, we looked at what happens after an attacker gets inside an environment. The credentials they find can determine how fast and how far they move into other systems. AI is compressing that timeline, and developer machines are where many of those credentials sit.
Finding exposed credentials is only half of the job. The harder part is fixing them without disrupting the way developers work. In this post we’ll cover how 1Password Developer Watchtower and 1Password Environments help teams find, replace, and manage developer secrets.
For many developers, the fastest place to put a secret is a local .env file. It is familiar, supported by the tools they already use, and usually stored in plaintext. Even when teams provide dedicated secrets tooling, it can feel slow and disconnected from the workflow, so the familiar path wins. That habit feeds secret sprawl, and the numbers are moving the wrong way. GitGuardian's 2026 State of Secrets Sprawl report found 28.65 million new secrets in public GitHub commits in 2025, up 34% from the previous year. Leaked secrets for AI services grew 81% in a single year.
For security teams, the bigger problem is visibility. A plaintext credential on a laptop is harder to monitor, rotate, revoke, or trace to the systems that depend on it. And now that AI coding assistants can access project files and run terminal commands, those credentials may be readable by more than the developer who created them. That is the gap 1Password is closing with 1Password Environments and Developer Watchtower. They help teams find improperly stored developer credentials, secure them where employees already trust, and let developers keep using them without slowing down work.
Developer Watchtower finds plaintext developer credentials on local devices, including .env files, and guides users to import them into 1Password
Developer credential visibility for admins adds reporting and remediation workflows so that security teams can see credential risk across the organization
1Password Environments gives developers a secure place to store, share, and use the secrets behind apps, services, automations, and AI-assisted workflows
Together, they give developers a safer way to use the credentials their work depends on, and give security teams the visibility and control to act before those credentials spread.
Developer Watchtower already identified plaintext SSH keys on a developer's device. It now also covers .env files, one of the most common places secrets end up during local development.
When the 1Password desktop app finds credentials in a local .env file, the developer gets an alert explaining the risk and offering a one-click import into 1Password Environments. The alert lets the user know which secrets may be exposed and makes it easy to move the secret into a secure 1Password vault.
For security teams, credentials that were invisible on local devices become something you can manage, share, govern, and remediate. Admins get a new report, local disk exposure, showing the plaintext .env files and SSH keys the desktop app found on local disks. With Developer Watchtower, admins can see which users and devices are affected without seeing the secret itself. That keeps the underlying value from being exposed and lets developers replace the credential without breaking the workflow. 1Password Environments is built into the desktop app. It gives developers a familiar place to store API keys, access tokens, database passwords, cloud credentials, and environment variables their apps need without leaving plaintext secrets in .env files or anywhere else on disk. Instead of reading from a file, the app requests its variables when it needs them and 1Password supplies them. There is no standing .env file for an attacker, or an AI tool with file access, to find. It keeps the one-click convenience that makes .env files appealing, backed by 1Password's security.
Developers don’t need to rebuild workflows to use managed secrets. With 1Password Environments you can:
Import an existing .env file or add variables manually, organized by app, service, project, or stage
Use the 1Password CLI and SDKs with the tools you already rely on, with local desktop authentication such as biometrics where available
Connect service accounts to support automation
Use supported AI coding workflows with managed secrets through 1Password's MCP Server, without copying secrets values into project files or pasting them into the model context
For Teams and Business customers, Environments fits into the access controls you already use in 1Password. You can share an environment with a group instead of adding people one at a time, while admins control whether Environments are available across the organization in the desktop app, CLI, and SDKs.
Turn on Developer Watchtower and review the Local disk exposure report. Assume any credential it finds may have been exposed. Revoke or rotate it, then move the replacement into Environments so it doesn’t end up back in a plaintext file.
The aim is to make the secure path the fast path. With security built into the workflows developers use, the habits that created exposure can also be the ones that fix it.
If you already use 1Password, Developer Watchtower is available at no extra cost. Explore Developer Watchtower, or see how to set up these features in the 1Password developer docs. Find plaintext secrets in .env files, secure them with 1Password Enterprise Password Manager, and keep using them as environment variables.
1Password Developer Tools fit into local development, CI/CD, and AI-assisted coding tools teams already use. Find a simpler way to give apps and automation the credentials they need without copying secrets.