Postman silently auto-installs AI plugins and attempts to share all API data
READ THE ORIGINAL SOURCEOpen original sourcegithub.com · Opens in a new tabExternal source links are regularly re-checked for safety, and checked again before opening using a recent cached result when available. How link checks work →
A GitHub issue reports that Postman desktop 12.33.4 automatically installed Codex and Claude Code plugins on an existing user's Mac. The reporter cites Postman's own log stating auto-existing-upgrade installation, a global Codex config change, a SessionStart hook instructing agents to load a Postman API skill for broad API tasks, and an installer source attempting to approve its own hook. The report describes unwanted integration and instruction changes and states it does not claim data exfiltration. Observations are from one Mac and not reproduced on a clean system.
One primary source; other links are context, not independent corroboration.
- Primary sourceHacker News · AI
- Discovery linkHacker News
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Open full article view →- Community discussion+5
- Fetched source page+30
- No editor link review+0
- Community link+0
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
A GitHub issue reports that Postman desktop 12.33.4 automatically installed Codex and Claude Code plugins on an existing user's Mac. The reporter cites Postman's own log stating auto-existing-upgrade installation, a global Codex config change, a SessionStart hook instructing agents to load a Postman API skill for broad API tasks, and an installer source attempting to approve its own hook. The report describes unwanted integration and instruction changes and states it does not claim data exfiltration. Observations are from one Mac and not reproduced on a clean system.
A READER'S EVIDENCE CHECKHow to read this signalSix questions about claims, sources, risks, and open checks
This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →
- 01Who is making each claim?
The claimant and whether each claim was measured or asserted are not recorded in this public brief.
- 02What was actually tested?
Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.
- 03Where are the sources?
Original link: github.com. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.
- 04What could mislead?
Source claims not independently checked; the issue is a user report from one machine and the reporter notes the trust record alone does not prove who created it.
- 05What is at risk if wrong?
Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.
- 06What would change the view?
No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.
Key findings from the stored brief
- Postman's log records automatic installation of Codex and Claude Code plugins for an existing user.
- The installed SessionStart hook tells agents to load a Postman skill before non-trivial API tasks.
- Installer source calls approvePostmanHook after installation to trust its own hook, per the report.
- The reporter states the report does not establish data exfiltration and was not reproduced on a clean Mac.
Source claims not independently checked; the issue is a user report from one machine and the reporter notes the trust record alone does not prove who created it.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
It raises consent and trust-boundary questions for desktop apps that modify other AI coding agents' configuration and hooks without explicit opt-in, affecting user control over agent behavior.
Limits and open questions
Source claims not independently checked; the issue is a user report from one machine and the reporter notes the trust record alone does not prove who created it.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →