Supply Chain Attack
A cybersecurity attack method in which adversaries compromise upstream software dependencies—such as open-source packages or build tools—to achieve large-scale infiltration by exploiting trust relationships. Notable examples include the SolarWinds incident and npm package poisoning events.
Core Facts
GPG signing is a digital signature mechanism based on asymmetric encryption; in GitHub's release workflow, maintainers use a private key to sign release artifacts, and users can verify the signature's validity using a public key.
Backdoor code was planted in the 2020 SolarWinds supply chain attack.
A software supply chain attack refers to an attack method in which the attacker poisons upstream dependency components to infect downstream users en masse.
Timeline (last 90 days)
Typical supply chain attack methods include soldering an extra tiny chip onto the printed circuit board, tampering with the firmware flashing process, or swapping the device during the logistics stage.
Motives for attacks on cold chain equipment may include extortion, sabotage and showing off, as well as reconnaissance for a supply chain attack.
If signature verification is bypassed, the private key is leaked, or the update server and download channel are hijacked, an attacker can push arbitrary code to users' machines.
供应链攻击指攻击者不直接瞄准最终目标，而是入侵其信任的第三方供应商、服务商或软件更新渠道，借助信任关系渗透进目标网络。
缓解供应链攻击的措施包括：要求供应商提供安全审计报告、在合同中明确安全责任、对远程管理接口实施多因素认证与访问控制。
A supply chain attack refers to an attack in which the attacker does not directly compromise the target system, but instead achieves the attack indirectly by contaminating upstream software, tools, or services that the target depends on.
Supply chain attacks can implant backdoors at the hardware or firmware level, bypassing the wallet's own cryptographic protections to steal private keys or mnemonic phrases from the physical source.
Supply chain attacks targeting hardware wallets are generally divided into two categories: physical-layer tampering and firmware-layer tampering.
Typical supply chain attack vectors targeting model repositories include embedding executable malicious code in pickle-format model weight files, replacing datasets for data poisoning, and modifying model card code examples to plant backdoors.
Third-party Skill code of unknown origin may contain malicious logic, which constitutes a supply chain attack risk within the field of software supply chain security.
17 more timeline events
All Facts (20)
GPG signing is a digital signature mechanism based on asymmetric encryption; in GitHub's release workflow, maintainers use a private key to sign release artifacts, and users can verify the signature's validity using a public key.
90%VerifiedBackdoor code was planted in the 2020 SolarWinds supply chain attack.
85%VerifiedA software supply chain attack refers to an attack method in which the attacker poisons upstream dependency components to infect downstream users en masse.
80%VerifiedCommon techniques in NPM supply chain attacks include typosquatting, hijacking abandoned legitimate packages, and phishing to obtain maintainer account credentials before injecting malicious versions.
65%VerifiedThe logic of a supply chain attack is that the attacker only needs to compromise one widely depended-upon link to reach multiple high-value targets.
65%VerifiedThe over-concentration of model distribution and version management in the AI ecosystem on a small number of platforms amplifies the risks of single points of failure and supply chain attacks.
65%VerifiedThe ua-parser-js supply chain attack occurred in 2021.
90%Partially VerifiedA supply chain attack refers to an attack in which the attacker does not directly compromise the target system, but instead achieves the attack indirectly by contaminating upstream software, tools, or services that the target depends on.
65%UnverifiedTypical supply chain attack methods include soldering an extra tiny chip onto the printed circuit board, tampering with the firmware flashing process, or swapping the device during the logistics stage.
50%UnverifiedIf signature verification is bypassed, the private key is leaked, or the update server and download channel are hijacked, an attacker can push arbitrary code to users' machines.
50%Unverified缓解供应链攻击的措施包括：要求供应商提供安全审计报告、在合同中明确安全责任、对远程管理接口实施多因素认证与访问控制。
50%Unverified供应链攻击指攻击者不直接瞄准最终目标，而是入侵其信任的第三方供应商、服务商或软件更新渠道，借助信任关系渗透进目标网络。
50%UnverifiedSupply chain attacks targeting hardware wallets are generally divided into two categories: physical-layer tampering and firmware-layer tampering.
50%UnverifiedSupply chain attacks can implant backdoors at the hardware or firmware level, bypassing the wallet's own cryptographic protections to steal private keys or mnemonic phrases from the physical source.
50%UnverifiedTypical supply chain attack vectors targeting model repositories include embedding executable malicious code in pickle-format model weight files, replacing datasets for data poisoning, and modifying model card code examples to plant backdoors.
50%UnverifiedThird-party Skill code of unknown origin may contain malicious logic, which constitutes a supply chain attack risk within the field of software supply chain security.
50%UnverifiedAttackers can hide malicious code in postinstall scripts, causing it to execute in the user's environment when downstream projects install dependencies, while remaining transparent to approval processes that only check package names and version numbers
50%UnverifiedMany so-called government agency leaks actually originate from vulnerabilities in third-party contractors, outsourced service providers, or affiliated systems, rather than from a breach of the target agency's own internal network.
50%UnverifiedMalicious actors planting backdoored models or tampering with weights on platforms such as Hugging Face could constitute supply chain attacks.
50%UnverifiedA mismatch between stated functionality and actual implementation is one of the most reliable heuristic signals for identifying malware.
50%