Loading vulnerability…
CVE-2025-62222 is a command injection vulnerability in the GitHub Copilot Chat extension for Visual Studio Code. The flaw is described as improper neutralization of special elements used in a command, allowing attacker-controlled input to influence command execution. A remote, unauthorized attacker can exploit the issue over a network to cause unintended command execution in the context available to the extension or its invoked processes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2025-62222, a vulnerability in GitHub Copilot Chat for Visual Studio Code. The exploit demonstrates how an attacker can craft a Python file with hidden prompt injection instructions in comments. When a victim opens this file in VS Code and interacts with Copilot Chat as instructed, Copilot is manipulated into suggesting a malicious PowerShell command. If the victim copies and executes this command, it opens a Meterpreter reverse shell to the attacker's machine, granting remote code execution. The repository contains a README.md with detailed attack and setup instructions, and a single Python file (copilot_injection_poc.py) containing the exploit logic via prompt injection. The attack vector is local, requiring user interaction and social engineering. No network endpoints are hardcoded, but the payload is designed to connect back to an attacker-controlled host as configured by the attacker.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.