←
1Password Developers672 posts
1Password Developers avatar

1Password Developers

@1PasswordDev

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

◷ Joined April 2026▧ 115 Photos and videos
1Password Developers avatar
1Password Developers@1PasswordDev·Nov 15

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. 🧵

Post attachment
1Password Developers avatar
1Password Developers@1PasswordDev·9h

Hackers are using always on agents to find your company’s secrets. Microsoft caught one going from exposed GitHub credentials to stealing data from Azure Key Vault in just 5 MINUTES. No need to manually hunt for secrets. Agents can do it at machine speed. Your leaked API key is now a ticking clock.

1Password Developers avatar
1Password Developers@1PasswordDev·16h

4/ Four ways to protect your credentials: 1. Use phishing-resistant MFA like passkeys or security keys. 2. Verify service alerts directly in the Microsoft 365 admin center. 3. Monitor suspicious logins, OAuth grants, and inbox rules. 4. If credentials were entered, reset them and revoke active sessions. The lesson: a real outage can become the perfect phishing lure. Source: microsoft.com/en-us/security…

1Password Developers avatar
1Password Developers@1PasswordDev·16h

3/ Why does this matter? One stolen Microsoft 365 login could give attackers access to: → Corporate email → Teams conversations → SharePoint and OneDrive files → Internal phishing opportunities And if sessions or tokens are compromised, changing a password alone may not be enough.

1Password Developers avatar
1Password Developers@1PasswordDev·16h

2/ Here’s where credential harvesting comes in. The restore button redirected users through tracking links to non-Microsoft domains. Microsoft suspects the campaign was designed to steal login credentials. But it hasn’t confirmed that any passwords were captured.

1Password Developers avatar
1Password Developers@1PasswordDev·16h

1/ The attackers used a real event. After a Microsoft 365 outage on November 12, phishing emails appeared claiming messages were being held. Employees were told to click “RESTORE MESSAGES” within 24 hours or lose their emails. The outage made the fake alerts more believable.

1Password Developers avatar
1Password Developers@1PasswordDev·16h

Hackers exploited a real Microsoft 365 outage to launch a massive phishing campaign. The goal? Likely credential theft. Fake Microsoft alerts told employees they had 24 hours to recover missing emails. Here’s how the attack worked and 4 ways to protect your credentials. 🧵

Post attachment
1Password Developers avatar
⟳ 1Password Developers retweeted
1Password Developers@1PasswordDev·17h

Congrats to @Cognition on the launch of Devin Bots. When a Devin Bot spins up a team of agents for a weeks-long project, how are you keeping all those credentials secure?

1Password Developers avatar
⟳ 1Password Developers retweeted
1Password Developers@1PasswordDev·19h

Upgrades, people. Upgrades. 🤝 Smarter agents → more tasks that need a secure login. @1PasswordDev for AI and agents is coming to OpenAI dots as well, so they can sign in while your credentials stay secure: x.com/JamesZmSun/status/2122…

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.

Post attachment
1Password Developers avatar
⟳ 1Password Developers retweeted
1Password Developers@1PasswordDev·Nov 17

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)

1Password Developers avatar
1Password Developers@1PasswordDev·Nov 17

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.

1Password Developers avatar
1Password Developers@1PasswordDev·Nov 17

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.

1Password Developers avatar
1Password Developers@1PasswordDev·Nov 17

3. Monitor JavaScript running in production. Your code review won’t catch malicious changes made inside a vendor’s platform. Alert on unexpected script changes, new external domains, and suspicious network requests. Passing CI doesn’t mean your browser is safe.

1Password Developers avatar
1Password Developers@1PasswordDev·Nov 17

2. Enforce a strict Content Security Policy (CSP). Limit which domains can execute scripts and receive data. Use nonces or hashes where practical. Monitor CSP violations. A well-designed policy can block unexpected payloads, even when a trusted script is compromised.

1Password Developers avatar
1Password Developers@1PasswordDev·Nov 17

1. Audit every third-party script. Analytics, A/B testing, chat widgets, and marketing tools all execute code in your users’ browsers. Know what you’re loading, who can change it, and whether you actually need it. Trusted vendors can become attack vectors.