1Password Developers

Official updates for developers building with @1Password.

Securely manage API keys, credentials, and agent access without exposing your secrets.

[1Password Developers @1PasswordDev]

The internet has a second audience: AI agents. 🤖

@Cloudflare just shared some fascinating data about how the web is changing.

Here are 3 things that caught our attention 🧵👇

[1Password Developers @1PasswordDev]

@HochstatMichael We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@ela_euk We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@joy_gajjar27 We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@adeilsonrbrito We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@AndAIyou We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@davzer_ @dd_pwnd We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@karan_luthra_ai We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@Han7162164272 We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@harisn We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@inferencepoint We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@prasad_pilla We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@XavierRiveraX We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@jayzhoupro We explained in details what happened here: https://t.co/via3M6fnSW

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

@thedealdirector We explained in details what happened here: https://t.co/via3M6fVIu

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

The lesson goes beyond Cursor.

AI coding-agent traces, logs, and support tickets can all become unexpected places where credentials are exposed.

We scan code for secrets.

But are we scanning what our AI agents leave behind?

Full disclosure:
https://t.co/gzdP2MkTX5

[1Password Developers @1PasswordDev]

Attackers distributed a malicious Claude Code extension through Cursor’s marketplace.

Up to 5,000 users may have received it.

But the attack didn’t start with the extension.

It started with an exposed vendor key and credentials buried in old AI coding-agent traces.

Here’s the attack chain. 🧵

[1Password Developers @1PasswordDev]

The malicious extension attempted to install a persistent SSH backdoor.

It added an attacker-controlled SSH key, collected host information, and installed persistence mechanisms.

The reverse tunnel generally failed without admin privileges.

But uninstalling alone may not remove the malware.