<?xml version="1.0" encoding="UTF-8"?>
<post>
  <id>01a01f8d-b903-7431-b5d7-c35aaa89707f</id>
  <type>post</type>
  <thread>
    <item>
      <id>01a01f8d-b903-7431-b5d7-c35aaa89707f</id>
      <depth>0</depth>
      <author>Kevin Sugar</author>
      <url>https://vutuv.de/k_sugar/posts/01a01f8d-b903-7431-b5d7-c35aaa89707f</url>
      <published_on>2026-08-20</published_on>
      <in_reply_to_id/>
      <author_username>k_sugar</author_username>
      <body_markdown>There&apos;s a **Rust supply chain attack going around right now**, the arrayref crate got compromised (along with internment and append-only-vec) after apparently getting republished from a hijacked account, pulling in a malicious proc-macro1 dependency that runs a shady build script.

The Rust Security Team has already deleted the bad versions, but if you pulled dependencies in the last few hours, it&apos;s worth double-checking. Malicious versions to watch for:

* arrayref@0.3.10

* internment@0.8.7

* append-only-vec@0.1.9

* proc-macro1, proc-macro-en, aovine, arone, aronenao, tinymember (any version)

  Supply chain attack on arrayref | Rust B...

Quick way to check if you&apos;ve cached any of these locally:

```
find ~/.cargo/registry/cache -type f \( \
  -name &apos;append-only-vec-0.1.9.crate&apos; -o \
  -name &apos;arrayref-0.3.10.crate&apos; -o \
  -name &apos;internment-0.8.7.crate&apos; -o \
  -name &apos;proc-macro1-*.crate&apos; -o \
  -name &apos;proc-macro-en-*.crate&apos; -o \
  -name &apos;aovine-*.crate&apos; -o \
  -name &apos;arone-*.crate&apos; -o \
  -name &apos;aronenao-*.crate&apos; -o \
  -name &apos;tinymember-*.crate&apos; \) -print

```

Full writeup from the Rust team here: [blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref](https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref/)</body_markdown>
      <in_reply_to_author/>
    </item>
  </thread>
  <description>There&apos;s a **Rust supply chain attack going around right now**, the arrayref crate got compromised (along with internment and append-only-vec) after apparently getting republished from a hijacked accou</description>
  <title>Kevin Sugar · 2026-08-20</title>
  <author>
    <name>Kevin Sugar</name>
    <username>k_sugar</username>
    <url>https://vutuv.de/k_sugar</url>
  </author>
  <replies/>
  <url>https://vutuv.de/k_sugar/posts/01a01f8d-b903-7431-b5d7-c35aaa89707f</url>
  <formats>
    <json>https://vutuv.de/k_sugar/posts/01a01f8d-b903-7431-b5d7-c35aaa89707f.json</json>
    <text>https://vutuv.de/k_sugar/posts/01a01f8d-b903-7431-b5d7-c35aaa89707f.txt</text>
    <markdown>https://vutuv.de/k_sugar/posts/01a01f8d-b903-7431-b5d7-c35aaa89707f.md</markdown>
    <xml>https://vutuv.de/k_sugar/posts/01a01f8d-b903-7431-b5d7-c35aaa89707f.xml</xml>
  </formats>
  <tags>
    <item>Rust</item>
    <item>security</item>
    <item>supply chain attack</item>
  </tags>
  <in_reply_to/>
  <generated_at>2026-09-03T01:54:20Z</generated_at>
  <schema_version>3</schema_version>
  <published_on>2026-08-20</published_on>
  <images/>
  <like_count>2</like_count>
  <license/>
  <review/>
  <fediverse_reaction_count>0</fediverse_reaction_count>
  <reply_count>0</reply_count>
  <fediverse_replies/>
  <body_markdown>There&apos;s a **Rust supply chain attack going around right now**, the arrayref crate got compromised (along with internment and append-only-vec) after apparently getting republished from a hijacked account, pulling in a malicious proc-macro1 dependency that runs a shady build script.

The Rust Security Team has already deleted the bad versions, but if you pulled dependencies in the last few hours, it&apos;s worth double-checking. Malicious versions to watch for:

* arrayref@0.3.10

* internment@0.8.7

* append-only-vec@0.1.9

* proc-macro1, proc-macro-en, aovine, arone, aronenao, tinymember (any version)

  Supply chain attack on arrayref | Rust B...

Quick way to check if you&apos;ve cached any of these locally:

```
find ~/.cargo/registry/cache -type f \( \
  -name &apos;append-only-vec-0.1.9.crate&apos; -o \
  -name &apos;arrayref-0.3.10.crate&apos; -o \
  -name &apos;internment-0.8.7.crate&apos; -o \
  -name &apos;proc-macro1-*.crate&apos; -o \
  -name &apos;proc-macro-en-*.crate&apos; -o \
  -name &apos;aovine-*.crate&apos; -o \
  -name &apos;arone-*.crate&apos; -o \
  -name &apos;aronenao-*.crate&apos; -o \
  -name &apos;tinymember-*.crate&apos; \) -print

```

Full writeup from the Rust team here: [blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref](https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref/)</body_markdown>
  <bookmark_count>0</bookmark_count>
  <fediverse_like_count>0</fediverse_like_count>
  <fediverse_reactions/>
  <fediverse_reply_count>0</fediverse_reply_count>
  <fediverse_repost_count>0</fediverse_repost_count>
  <likers>
    <item>
      <name>Andres Correa Casablanca</name>
      <username>andreu</username>
      <url>https://vutuv.de/andreu</url>
    </item>
    <item>
      <name>Mihail Moroşan</name>
      <username>morosanmihail</username>
      <url>https://vutuv.de/morosanmihail</url>
    </item>
  </likers>
  <repost_count>0</repost_count>
  <thread_truncated>false</thread_truncated>
  <verified_author_links/>
</post>
