[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"framework:mitre-attack\u002Ft1195-001":3},{"item":4,"lessons":18,"controls":69,"related":97},{"family":5,"item":6,"code":7,"title":8,"citations":9,"publisher":10,"summary_md":11,"official_text":12,"official_attribution":13,"official_url":14,"link_label":15,"note":16,"updated_at":17},"mitre-attack","t1195-001","T1195.001","Compromise Software Dependencies and Development Tools",5,"MITRE","**What attackers do.** Attackers tamper with software dependencies and development tools, such as open source packages, build tools or code editor plugins, so that the compromise spreads into the software built with them. This serves Initial Access.\n\n**How to defend.** Pin dependency versions, use lock files and internal package mirrors, and scan dependencies for known malicious packages. Protect developer workstations and build systems, require code review for dependency changes and keep a software bill of materials. Run builds in isolated, monitored environments with restricted network access.\n\n**Signs to look for.** Look for new or renamed packages similar to popular ones, install scripts making network connections, unexpected changes in package maintainers and build systems contacting unknown domains. A common gap is developer machines having broad access with little monitoring.","Adversaries may manipulate software dependencies and development tools prior to receipt by a final consumer for the purpose of data or system compromise. Applications often depend on external software to function properly. Popular open source projects that are used as dependencies in many applications, such as pip and NPM packages, may be targeted as a means to add malicious code to users of the dependency. This may also include abandoned packages, which in some cases could be re-registered by threat actors after being removed by adversaries. Adversaries may also employ \"typosquatting\" or name-confusion by choosing names similar to existing popular libraries or packages in order to deceive a user.\n\nAdditionally, CI\u002FCD pipeline components, such as GitHub Actions, may be targeted in order to gain access to the building, testing, and deployment cycles of an application. By adding malicious code into a GitHub action, a threat actor may be able to collect runtime credentials (e.g., via Proc Filesystem) or insert further malicious components into the build pipelines for a second-order supply chain compromise. As GitHub Actions are often dependent on other GitHub Actions, threat actors may be able to infect a large number of repositories via the compromise of a single Action.\n\nAdversaries may also target the configuration and instruction files consumed by integrated development environments and AI coding agents. Project files such as tasks.json may execute commands when a developer opens or builds a project, while agent skill files (SKILL.md) supply an agent with instructions and resources that it loads on demand and runs with the permissions of the agent process. To encourage downloads, adversaries may publish these files under benign-appearing or typo-squatted names, upload unmodified copies of the genuine skills first so the listings accumulate installs before the content behind them is weaponized, or may place the malicious instructions in a secondary document that the reviewed entry point references. Because these artifacts are natural language or configuration rather than executable code, they may pass registry screening and signature-based scanning.","© The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (MITRE ATT&CK®).","https:\u002F\u002Fattack.mitre.org\u002Ftechniques\u002FT1195\u002F001\u002F","Open the technique on MITRE ATT&CK",null,"2026-10-18T15:18:43.664+00:00",{"total":19,"list":20},15,[21,25,29,33,37,41,45,49,53,57,61,65],{"slug":22,"title":23,"published_at":24},"fake-interview-assignments-weaponize-npm-packages-to-compromise-developer-machines","Fake Interview Assignments Weaponize npm Packages to Compromise Developer Machines","2026-11-13T18:21:36.396+00:00",{"slug":26,"title":27,"published_at":28},"compromised-github-accounts-weaponized-to-poison-thousands-of-repositories","Compromised GitHub Accounts Weaponized to Poison Thousands of Repositories","2026-11-13T10:20:30.167+00:00",{"slug":30,"title":31,"published_at":32},"mcp-server-pinning-drift-exposes-ai-coding-assistants-to-malicious-dependencies","MCP Server 'Pinning Drift' Exposes AI Coding Assistants to Malicious Dependencies","2026-11-13T06:20:23.867+00:00",{"slug":34,"title":35,"published_at":36},"60000-github-repos-poisoned-via-hijacked-accounts-and-workflow-injection","60,000 GitHub Repos Poisoned via Hijacked Accounts and Workflow Injection","2026-11-12T14:21:55.79+00:00",{"slug":38,"title":39,"published_at":40},"net-11-hardens-nuget-and-container-pipelines-against-supply-chain-attacks",".NET 11 Hardens NuGet and Container Pipelines Against Supply Chain Attacks","2026-11-12T09:20:38.657+00:00",{"slug":42,"title":43,"published_at":44},"stolen-github-credentials-enable-mass-ci-secret-theft-across-tens-of-thousands-of-repositories","Stolen GitHub Credentials Enable Mass CI Secret Theft Across Tens of Thousands of Repositories","2026-11-12T03:20:21.953+00:00",{"slug":46,"title":47,"published_at":48},"browser-extensions-are-a-silent-supply-chain-threat","Browser Extensions Are a Silent Supply-Chain Threat","2026-11-11T20:20:24.025+00:00",{"slug":50,"title":51,"published_at":52},"ai-coding-assistant-mcp-servers-expose-api-keys-via-poisoned-dependencies","AI Coding Assistant MCP Servers Expose API Keys via Poisoned Dependencies","2026-11-11T17:20:58.508+00:00",{"slug":54,"title":55,"published_at":56},"open-source-package-registries-require-active-threat-filtering-not-just-policy-checks","Open-Source Package Registries Require Active Threat Filtering, Not Just Policy Checks","2026-11-11T04:20:24.893+00:00",{"slug":58,"title":59,"published_at":60},"git-integer-truncation-flaw-enables-code-execution-via-malicious-repositories","Git Integer Truncation Flaw Enables Code Execution via Malicious Repositories","2026-11-10T20:21:01.14+00:00",{"slug":62,"title":63,"published_at":64},"malicious-vs-code-extensions-deliver-malware-loaders-via-themed-packages","Malicious VS Code Extensions Deliver Malware Loaders via Themed Packages","2026-10-02T16:21:36.884+00:00",{"slug":66,"title":67,"published_at":68},"xcsset-malware-targets-macos-devs-through-poisoned-xcode-projects","XCSSET Malware Targets macOS Devs Through Poisoned Xcode Projects","2026-08-04T20:20:20.234+00:00",[70,75,80,84,88,93],{"slug":71,"name":72,"problem":73,"stories":74},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship.",11,{"slug":76,"name":77,"problem":78,"stories":79},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",8,{"slug":81,"name":82,"problem":83,"stories":9},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":85,"name":86,"problem":87,"stories":9},"security-awareness-training","Security awareness training and phishing simulation","People recognise and report attacks instead of falling for them.",{"slug":89,"name":90,"problem":91,"stories":92},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",3,{"slug":94,"name":95,"problem":96,"stories":92},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",[98,103,109,114,119,125,130,134],{"family":99,"item":100,"code":101,"title":102,"together":74},"nist-800-53","sa-12","SA-12","Supply Chain Protection",{"family":104,"item":105,"code":106,"title":107,"together":108},"cis","16","Control 16","Application Software Security",9,{"family":110,"item":111,"code":112,"title":113,"together":79},"nis2","21-2-d","Article 21(2)(d)","Supply chain security (Article 21(2)(d))",{"family":104,"item":115,"code":116,"title":117,"together":118},"2","Control 2","Inventory and Control of Software Assets",7,{"family":120,"item":121,"code":122,"title":123,"together":124},"nist-sp","800-161","SP 800-161","SP 800-161 Rev. 1: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations",4,{"family":126,"item":127,"code":128,"title":129,"together":124},"nist-csf","id-sc","ID.SC-4","Supply Chain Risk Management (CSF 1.1)",{"family":126,"item":131,"code":132,"title":133,"together":92},"de-cm","DE.CM-1","Continuous Monitoring",{"family":120,"item":135,"code":136,"title":137,"together":92},"800-218","SP 800-218","SP 800-218: Secure Software Development Framework (SSDF) Version 1.1"]