1Password Developers (@1PasswordDev) header
1Password Developers (@1PasswordDev) profile picture

Official updates for developers building with @1Password. Securely manage API keys, credentials, and agent access without exposing your secrets.

Joined April 2026
Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)Photo by 1Password Developers (@1PasswordDev)
The FBI just issued a warning about AI agents being used to hack companies. Some attacks reached privileged access in under 3 HOURS. 67,000 people's data exposed. 2,250+ downstream tenants affected in a separate campaign. The tool behind it? ARTEX. Here's how the attacks work. 🧵
21
174
22
757
110,390
178 organizations. One compromised third-party platform. Attackers exploited Optimizely to inject malicious JavaScript into websites including Zoom, CNN, BBC, and Salesforce. The code could steal payment data, hijack crypto transactions, and target iPhones. 5 things developers can do to protect themselves 🧵
1
3
35
3,143
4. Protect credentials and sessions. Use HttpOnly, Secure, and SameSite cookies. Avoid storing sensitive tokens in localStorage. Give vendor integrations least-privilege access and require MFA for admin accounts. Reduce what compromised JavaScript can steal.
1
137
5. Isolate sensitive workflows. Keep payment details inside trusted hosted payment fields. Minimize third-party scripts on login, checkout, and account pages. The lesson from Optimizely: Your application is only as secure as the JavaScript you let execute inside it.
128
1Password Developers retweeted
We’re starting to test 1password in dots! Our goal is to make it easy for your dot to do tasks that require a login, while keeping your credentials secure. Excited to roll this out more broadly soon. Let us know what you think.
150
64
17
1,327
71,428
Google believes it has found the first cyberattack run end to end by AI. A framework compared software before and after each patch, worked out the bug, wrote the exploit, and launched it. No human in the loop. Here's what it means for anyone in Tech 🧵(1/9)
5
41
2
312
134,283
What Mandiant's guidance recommends: 1. Lock down admin systems 2. Use short-lived credentials 3. Limit access 4. Segment networks 5. Watch for spikes in API and identity activity For AI services: set budget alerts and scan your code for leaked keys. 🧵(9/10)
1
1
4
372
We've reviewed this product. Great uptime, no breaking changes since the invention of paper. The API documentation is a little thin, though.
Password managers ARE SO COOKED $10 lifetime
10
7,395
1Password Developers retweeted
1Password Environments + their MCP server is the strongest practical option right now. Create a project-scoped Environment, connect the agent via MCP. The agent can list names, create mounts, and manage config, but the server never returns secret values. Secrets inject only into the runtime process (in-memory mount or op run). Pair it with the agent’s deny rules so it cannot Read(.env*). Prefer short-lived tokens. This keeps the vault out of the agent’s context entirely.
2
1
1
6
8,487
For securing your AI coding agents, @grok recommends @1PasswordDev Environments + its MCP server as the strongest practical option, as well as the 1Password Credential Broker. If you want to try it or have questions about it, please connect or comment in the thread.
1Password Environments + their MCP server is the strongest practical option right now. Create a project-scoped Environment, connect the agent via MCP. The agent can list names, create mounts, and manage config, but the server never returns secret values. Secrets inject only into the runtime process (in-memory mount or op run). Pair it with the agent’s deny rules so it cannot Read(.env*). Prefer short-lived tokens. This keeps the vault out of the agent’s context entirely.
22
7,840