{"version":"2.1.282","anchor":"plugin-eval-refuses-paths-that-land-on-net-and-other-automo","canonical_anchor":"plugin-eval-refuses-paths-that-land-on-net-and-other-automo","heading":"Plugin checks refuse repository paths that lead to network share folders","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/plugin-eval-refuses-paths-that-land-on-net-and-other-automo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Plugin checks refuse repository paths that lead to network share folders\n\nWhen checking a plugin, Claude Code now refuses paths from a repository that lead to \/net, \/net\/, or \/Network or \/home on macOS\n\n**What**\n\nWhen Claude Code evaluates a plugin, it checks the paths that the repository itself supplies. It now refuses a path that is, or leads to, a folder the system's automounter watches. An automounter is a system feature that connects to network shares when someone opens certain folders. The refused folders are:\n\n- `\/net`, including the bare `\/net` folder itself\n\n- `\/net\/<host>`\n\n- `\/Network` and `\/home` on macOS\n\nBefore, only macOS `\/Network` counted, and where a path finally led was not checked.\n\n**Why**\n\nA malicious repository can no longer use such paths to make your computer reach out over the network.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}