[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"framework:mitre-attack\u002Ft1195-001":3},{"item":4,"lessons":18,"controls":40,"related":69},{"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":9,"list":19},[20,24,28,32,36],{"slug":21,"title":22,"published_at":23},"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":25,"title":26,"published_at":27},"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",{"slug":29,"title":30,"published_at":31},"fakegit-campaign-weaponizes-7600-github-repos-to-hijack-ai-agents","FakeGit Campaign Weaponizes 7,600 GitHub Repos to Hijack AI Agents","2026-07-20T20:20:40.413+00:00",{"slug":33,"title":34,"published_at":35},"fake-poc-repos-deliver-rat-to-vulnerability-researchers","Fake PoC Repos Deliver RAT to Vulnerability Researchers","2026-07-02T08:20:19.52+00:00",{"slug":37,"title":38,"published_at":39},"legitimate-platforms-weaponized-across-28-attack-vectors-in-weekly-threat-surge","Legitimate Platforms Weaponized Across 28+ Attack Vectors in Weekly Threat Surge","2026-06-18T18:21:26.972+00:00",[41,46,51,55,60,65],{"slug":42,"name":43,"problem":44,"stories":45},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship.",4,{"slug":47,"name":48,"problem":49,"stories":50},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",3,{"slug":52,"name":53,"problem":54,"stories":50},"security-awareness-training","Security awareness training and phishing simulation","People recognise and report attacks instead of falling for them.",{"slug":56,"name":57,"problem":58,"stories":59},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",2,{"slug":61,"name":62,"problem":63,"stories":64},"ai-security","AI application security","Prompt injection, data leaks through AI tools and unapproved AI use get caught.",1,{"slug":66,"name":67,"problem":68,"stories":64},"endpoint-management","Device management (MDM and UEM)","Every company laptop and phone is known, encrypted, locked down and up to date.",[70,75,79,84,89,94,98,102],{"family":71,"item":72,"code":73,"title":74,"together":9},"cis","2","Control 2","Inventory and Control of Software Assets",{"family":71,"item":76,"code":77,"title":78,"together":45},"16","Control 16","Application Software Security",{"family":80,"item":81,"code":82,"title":83,"together":45},"nist-sp","800-161","SP 800-161","SP 800-161 Rev. 1: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations",{"family":85,"item":86,"code":87,"title":88,"together":45},"nist-800-53","sa-12","SA-12","Supply Chain Protection",{"family":90,"item":91,"code":92,"title":93,"together":50},"nist-csf","id-sc","ID.SC-4","Supply Chain Risk Management (CSF 1.1)",{"family":80,"item":95,"code":96,"title":97,"together":50},"800-218","SP 800-218","SP 800-218: Secure Software Development Framework (SSDF) Version 1.1",{"family":85,"item":99,"code":100,"title":101,"together":59},"si-7","SI-7","Software, Firmware, and Information Integrity",{"family":5,"item":103,"code":104,"title":105,"together":59},"t1059","T1059","Command and Scripting Interpreter"]