The custom HTTP SSRF guard checks DNS results but does not pin the subsequent connection, leaving a DNS rebinding path to private addresses and metadata. Because this is a real security weakness in an explicitly invoked feature, classify it as suspicious rather than malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user explicitly runs a local custom HTTP column whose hostname can return a public address during validation and a private address when fetch resolves it.
Impact
A rebinding host may reach internal services or cloud metadata and could receive secrets configured for the request.
Mechanism
The code validates DNS results but discards the checked addresses, then fetches the hostname again without pinning the connection. Request templates can include configured local secrets.
Evidence
dist/local-custom-http-column.jsnode_modules/@oxygen/shared/dist/custom-http-safety.js
Network endpoints2
User-configured HTTPS custom HTTP URLoxygen-agent.com/api/cli/observability/diagnostics (diagnostics upload is opt-in)