Droundy
Monthly
Build-time malicious code execution in the arrayref Rust crate version 0.3.10 allows an attacker to run arbitrary code on any developer or CI machine that compiles a project depending on it. The compromised release pulls in a rogue transitive dependency that beacons to a command-and-control server and accepts arbitrary command execution, making this a confirmed supply-chain compromise disclosed by the Rust Security Response WG and RustSec (RUSTSEC-2026-0260). No public standalone exploit is needed because the crate itself is the payload; not currently listed in CISA KEV.
Build-time arbitrary code execution affects the append-only-vec Rust crate version 0.1.9, which was trojanized as part of the August 2026 arrayref-family supply chain attack. The crate pulls in a rogue dependency that beacons to a command-and-control server and offers the operator arbitrary code execution on any machine that compiles a project depending on it. This is classified CWE-506 (embedded malicious code); no public exploit tooling is published because the malware itself is the payload, and it is not listed in CISA KEV.
Build-time arbitrary code execution in the internment 0.8.7 crate for Rust: this specific published version was trojanized as part of the August 2026 arrayref/proc-macro1 Rust supply-chain campaign, pulling in a rogue transitive dependency that registers with a command-and-control server and executes attacker-supplied code on the developer or CI machine that compiles any project depending on it. Any Rust build that resolves internment 0.8.7 is affected, and because the payload runs during `cargo build` rather than at application runtime, compromise occurs before the target program is ever executed. No CISA KEV listing or public proof-of-concept is documented in the provided data, so this is tracked as embedded malicious code (CWE-506) rather than a confirmed in-the-wild exploit chain.
Build-time malicious code execution in the arrayref Rust crate version 0.3.10 allows an attacker to run arbitrary code on any developer or CI machine that compiles a project depending on it. The compromised release pulls in a rogue transitive dependency that beacons to a command-and-control server and accepts arbitrary command execution, making this a confirmed supply-chain compromise disclosed by the Rust Security Response WG and RustSec (RUSTSEC-2026-0260). No public standalone exploit is needed because the crate itself is the payload; not currently listed in CISA KEV.
Build-time arbitrary code execution affects the append-only-vec Rust crate version 0.1.9, which was trojanized as part of the August 2026 arrayref-family supply chain attack. The crate pulls in a rogue dependency that beacons to a command-and-control server and offers the operator arbitrary code execution on any machine that compiles a project depending on it. This is classified CWE-506 (embedded malicious code); no public exploit tooling is published because the malware itself is the payload, and it is not listed in CISA KEV.
Build-time arbitrary code execution in the internment 0.8.7 crate for Rust: this specific published version was trojanized as part of the August 2026 arrayref/proc-macro1 Rust supply-chain campaign, pulling in a rogue transitive dependency that registers with a command-and-control server and executes attacker-supplied code on the developer or CI machine that compiles any project depending on it. Any Rust build that resolves internment 0.8.7 is affected, and because the payload runs during `cargo build` rather than at application runtime, compromise occurs before the target program is ever executed. No CISA KEV listing or public proof-of-concept is documented in the provided data, so this is tracked as embedded malicious code (CWE-506) rather than a confirmed in-the-wild exploit chain.