Postman Auto-Installed Codex and Claude Code Plugins — SkimNews
Get the Tech newsletter
Daily tech — startups, AI labs, chips, the launches that shape the next decade. Free.
- Postman’s
main.logrecorded on October 24, 2026 anauto-existing-upgradescript completingclaude-code:installedandcodex:installedduring the reported desktop-app opening. - Codex’s global
~/.codex/config.tomladded Postman’s Git marketplace, enabledpostman@postman, and registered a SessionStart hook matchingstartup|clear|compact. postman:api-engineerwas to be loaded before any non-trivial API engineering task—including design, implementation, mocking, testing, monitoring, documentation and deployment—not only when a user explicitly requested Postman.- Postman’s installer called
approvePostmanHookafter installation, obtained the hook hash throughhooks/list, and usedconfig/batchWriteto upsert its trust state; the trust record alone does not prove user approval. - mcp.postman.com was configured as the remote MCP endpoint, but Codex logs recorded
Auth requiredduring initialization, leaving the connection without a working authenticated session. - Postman CLI was separately installed in
~/.local/binduring the same window in which Claude Code recorded user-scopepostman@claude-plugins-officialversion 2.0.1, with install and update timestamps of2026-10-24T09:34:02.610Z. - Postman desktop 12.33.4 was the version in the observed sequence on a signed-in Mac, but the sequence was not reproduced on a clean Mac and the evidence does not establish data exfiltration.
Why it matters: For signed-in Postman users, opening the desktop app reportedly reached two coding-agent hosts, rewrote global configuration and attempted to create a trusted hook without user action. Developers using Codex or Claude Code had API work redirected through Postman skills, though the evidence establishes unconsented integration changes rather than data exfiltration.
Ask SkimNews
