# teampcp-injects-malware-into-microsoft-linked-github-repositories: TeamPCP Injects Malware into Microsoft-Linked GitHub Repositories

> TeamPCP Injects Malware into Microsoft-Linked GitHub Repositories is a high-severity supply chain compromise issue in Azure / Azure-Samples / Microsoft GitHub repos touched, an AI agent. Affected: Azure / Azure-Samples / Microsoft GitHub repos touched 02:36-03:22 UTC 5 June 2026. It has been exploited in the wild.

- **Canonical URL:** https://catalog.anomity.ai/vuln/teampcp-injects-malware-into-microsoft-linked-github-repositories
- **Aliases:** ti-044
- **Severity:** high
- **Attack type:** Supply chain compromise, Malware
- **Component:** Azure / Azure-Samples / Microsoft GitHub repos touched (AI agent)
- **Exploited in the wild:** yes
- **Published:** 2026-06-05
- **Last verified:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/vuln/teampcp-injects-malware-into-microsoft-linked-github-repositories

## Summary

TeamPCP used a compromised GitHub account to inject malicious code into at least 42 repositories and 236 branches across the Azure, Azure-Samples, and Microsoft GitHub organizations (published 02:36-03:22 UTC on 5 June 2026). The malicious code remained in the GitHub repos and had not been pushed to other distribution channels as of disclosure.

## Affected versions

| Affected | Fixed in |
| --- | --- |
| Azure / Azure-Samples / Microsoft GitHub repos touched 02:36-03:22 UTC 5 June 2026 | no fixed version listed |

## Am I affected by this vulnerability?

You are affected if you run Azure / Azure-Samples / Microsoft GitHub repos touched 02:36-03:22 UTC 5 June 2026.

## How do I fix it?

Do not build from affected branches; verify commit provenance and pin to known-good SHAs. Review any clones/forks pulled around 5 June 2026 and scan for injected code before use.

## How do I find every machine running Azure / Azure-Samples / Microsoft GitHub repos touched?

Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run Azure / Azure-Samples / Microsoft GitHub repos touched and which version, then enforce a policy on it.

## References

- article: https://thehackernews.com/2026/06/miasma-malware-targets-npm-packages-and.html

## Related vulnerabilities

- [mandiant-hijacked-ai-coding-assistant-session-deploys-shai-hulud-across](https://catalog.anomity.ai/vuln/mandiant-hijacked-ai-coding-assistant-session-deploys-shai-hulud-across) — critical
- [chaindrop-opening-a-repository-is-enough-to-execute-attacker-code](https://catalog.anomity.ai/vuln/chaindrop-opening-a-repository-is-enough-to-execute-attacker-code) — critical
- [keyv-cacheable-npm-worm-writes-auto-run-hooks-into-claude-settings-json](https://catalog.anomity.ai/vuln/keyv-cacheable-npm-worm-writes-auto-run-hooks-into-claude-settings-json) — critical
- [asyncapi-npm-packages-backdoored-with-miasma-malware-framework](https://catalog.anomity.ai/vuln/asyncapi-npm-packages-backdoored-with-miasma-malware-framework) — critical
- [mini-shai-hulud-170-npm-pypi-packages-compromised-in-coordinated](https://catalog.anomity.ai/vuln/mini-shai-hulud-170-npm-pypi-packages-compromised-in-coordinated) — critical
- [self-propagating-npm-supply-chain-worm-targets-ai-agent-packages](https://catalog.anomity.ai/vuln/self-propagating-npm-supply-chain-worm-targets-ai-agent-packages) — critical

---

Source: Anomity Security Database (https://catalog.anomity.ai/vuln). Detect affected AI tools on developer devices: https://anomity.ai/?utm_source=catalog&utm_medium=vuln-md&utm_campaign=teampcp-injects-malware-into-microsoft-linked-github-repositories