tag: Developer-Tools · 5 items
- Engineer — Learn: If you expose Solana JSON-RPC or gRPC dev endpoints (e.g., surfpool) on public interfaces, audit firewall rules to ensure they are not internet-reachable; no active exploitation or PoC reported.
- SOC/IR — Learn: Awareness item: opportunistic scans targeting Solana dev endpoints are occurring, but no IOCs, TTPs, or confirmed exploitation are provided to act on.
- Leader — Skip
- Engineer — Act: If your team uses Open VSX-sourced extensions (common in Theia, Gitpod, or VS Code OSS environments), audit installed extensions against the 77 removed packages and remove any installed between July 26–August 1, 2026; check build/dev environments for unexpected outbound connections during that window.
- SOC/IR — Act: Hunt for anomalous outbound traffic from developer workstations and CI runners between July 26 and August 1, 2026 that may indicate data exfiltration from compromised extensions; correlate against Open VSX extension install events in endpoint logs.
- Leader — Plan: This incident illustrates supply-chain risk in developer tooling marketplaces; work with engineering leads this quarter to establish an approved-extension policy and inventory for IDE plugins used across the org.
- Engineer — Act: If your team uses Open VSX (common in VS Code OSS or VSCodium environments), audit installed extensions against the removed list and purge any matches; review extension installation policies in CI/CD or dev container configs to restrict to known-good sources.
- SOC/IR — Plan: Build or tune detections for unexpected outbound connections from IDE processes (code, codium) to unknown endpoints; consider hunting for extension-related network activity in EDR telemetry from developer workstations over the past 90 days.
- Leader — Learn: This incident illustrates ongoing supply-chain risk in developer tooling marketplaces; useful context for evaluating software vetting policies in engineering onboarding, but no immediate leadership action required.
- Engineer — Learn: If Codex is in your development toolchain or CI pipelines, review the repository for security boundaries, sandboxing limitations, and trust assumptions — no exploit pressure, but 536 HN upvotes suggests substantive security guidance worth absorbing.
- SOC/IR — Skip
- Leader — Learn: If developers in your organization use OpenAI Codex, this repository likely clarifies the product’s security posture and responsible-use boundaries — useful context for an AI tool risk policy, but no immediate action required.
- Engineer — Act: Public PoC exists for a symlink-based sandbox escape in Claude Code, which engineers and CI/CD pipelines commonly run; update Claude Code to the patched release immediately and audit any pipelines that invoke it with elevated filesystem access.
- SOC/IR — Learn: Low EPSS (0.01) and no active exploitation campaign; no IOCs or ATT&CK-mappable TTPs are provided, but the symlink sandbox-escape technique is worth noting if Claude Code runs in monitored developer environments.
- Leader — Skip
- Signals: CVE-2026-39861 — CISA KEV: not listed, EPSS 0.01, public PoC on GitHub