Solidity Pro VSCode Extension Poisoned; Check Old Versions

The compromise of a Solidity-focused VSCode extension hits at the developer toolchain rather than at deployed contracts, which is the more uncomfortable part: the poisoned code sits on the machines where keys, configs and deployment scripts live. Developers who installed historical versions carry the exposure regardless of what the extension does now, and the recommendation to audit old versions implies the tampering window is not fully mapped. The open question is whether other extensions in the same publishing orbit were touched, and whether a clearer timeline of affected versions follows.