Skip to content
GitHub·

🛡️Postman Silently Installed Agent Hooks on Macs Without Asking Users

Your agents may be routing API work into Postman

TL;DR

Postman v12.33.4 on macOS quietly installed a plugin, hook, remote MCP, and CLI for existing users, and an installer-approved hook told agents to send broad API work through Postman. If you use Codex or Claude Code on a Mac, check your configs now.

Postman just shipped one of the worst consent bugs we've seen from a developer tool this year. On October 25, 2026, opening Postman on a Mac silently installed agent plugins and a CLI for existing desktop users, then let the installer approve its own startup hook. Why you should care: if you run Codex or Claude Code, that hook told your agent to route broad API work into Postman. You'd see recurring MCP authentication warnings, and your agents would keep reaching for Postman skills even though the remote MCP connection never actually authenticated. Your global user config changed, and you probably didn't click anything. The numbers: Postman 12.33.4, Codex plugin 1.1.0, Claude plugin 2.0.1, all on macOS. The install touched global config, marketplaces, caches, the CLI, and the Postman log. Nothing in that list needs your opt-in, which is the whole problem. What to watch: the report asks Postman to halt automatic installs pending explicit opt-in, remove installer self-approval, and ship a full rollback path. Until that lands, audit your agent configs by hand.

Postman Silently Installed Agent Hooks on Macs Without Asking Users — GitHub

Key Points

1

The problem appeared on macOS with Postman 12.33.4, Codex plugin 1.1.0, and Claude plugin 2.0.1 installed, with the incident dated October 25, 2026 in the report.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

postmanmcpclaude-codecodexmacos

Comments

Subscribe to join the conversation...

Be the first to comment