A developer-targeting campaign leveraged malicious Next.js repositories to trigger a covert RCE-to-C2 chain through standard ...
What I've tried: Created multiple new PAT tokens with full access Verified PAT works perfectly via direct Azure DevOps REST API calls Tried both @azure-devops/mcp and @azure-devops/mcp@next versions ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results