<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Brenner Cruvinel - segurança</title>
    <subtitle>AI researcher and product designer building at the edge of computer science and mental health.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://brennercruvinel.blog/en/tags/seguranca/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://brennercruvinel.blog"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-04-08T00:00:00+00:00</updated>
    <id>https://brennercruvinel.blog/en/tags/seguranca/atom.xml</id>
    <entry xml:lang="en">
        <title>Extraction attacks against black-box models: a reading list</title>
        <published>2026-04-08T00:00:00+00:00</published>
        <updated>2026-04-08T00:00:00+00:00</updated>
        
        <author>
          <name>
            Brenner Cruvinel
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://brennercruvinel.blog/en/blog/model-extraction-attacks/"/>
        <id>https://brennercruvinel.blog/en/blog/model-extraction-attacks/</id>
        
        <content type="html" xml:base="https://brennercruvinel.blog/en/blog/model-extraction-attacks/">&lt;p&gt;I put this list together for a security and intelligence research project. The first version was a dump of search results: the same Tramèr paper showed up eight times under different links, and half the items had nothing to do with model extraction. I deduplicated it, checked every source and removed what was off topic. What remains is what I would read again.&lt;/p&gt;
&lt;p&gt;The question that ties it together: if I can only query a model through an API, without seeing the weights, how much of it can be rebuilt? And, going the other way, how much of the training data can be recovered from the model or from its gradients?&lt;/p&gt;
&lt;h2 id=&quot;stealing-the-model-through-the-api&quot;&gt;Stealing the model through the API&lt;/h2&gt;
&lt;p&gt;The starting point is &lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/1609.02943&quot;&gt;Stealing Machine Learning Models via Prediction APIs&lt;/a&gt;, by Tramèr and colleagues, presented at USENIX Security 2016. They showed that cloud machine learning services, by returning prediction confidence, let an attacker rebuild models such as logistic regression and decision trees with few queries. The code is at &lt;a rel=&quot;external&quot; href=&quot;https://github.com/ftramer/Steal-ML&quot;&gt;ftramer/Steal-ML&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/1602.02697&quot;&gt;Practical Black-Box Attacks against Machine Learning&lt;/a&gt;, by Papernot and colleagues, AsiaCCS 2017, is a close relative: it trains a substitute model by querying the target and uses that substitute to craft adversarial examples that transfer to the original.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/1812.02766&quot;&gt;Knockoff Nets&lt;/a&gt;, by Orekondy, Schiele and Fritz, CVPR 2019, steals the functionality of an image network by querying it with random natural images. &lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1609/aaai.v34i01.5432&quot;&gt;ActiveThief&lt;/a&gt;, by Pal and colleagues, AAAI 2020, does the same while choosing queries by active learning over unlabelled public data. &lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.14722/ndss.2020.24178&quot;&gt;CloudLeak&lt;/a&gt;, by Yu and colleagues, NDSS 2020, uses adversarial examples to extract models from commercial services with fewer queries.&lt;/p&gt;
&lt;p&gt;More recent: &lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/2409.14122&quot;&gt;Efficient and Effective Model Extraction&lt;/a&gt;, by Zhu and colleagues, 2024, and &lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1016/j.knosys.2024.112144&quot;&gt;A realistic model extraction attack against graph neural networks&lt;/a&gt;, by Guan and colleagues, in Knowledge-Based Systems 2024, which takes the problem to graph networks.&lt;/p&gt;
&lt;p&gt;The milestone for language models is &lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/2403.06634&quot;&gt;Stealing Part of a Production Language Model&lt;/a&gt;, by Carlini and colleagues, 2024. With API access alone, they recovered the final projection layer of production models and their hidden dimension.&lt;/p&gt;
&lt;p&gt;For the full map, the survey &lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1145/3595292&quot;&gt;I Know What You Trained Last Summer&lt;/a&gt;, by Oliynyk, Mayer and Rauber, ACM Computing Surveys 2023, covers attacks and defences, and the &lt;a rel=&quot;external&quot; href=&quot;https://github.com/kzhao5/ModelExtractionPapers&quot;&gt;kzhao5/ModelExtractionPapers&lt;/a&gt; repository keeps a list of papers in the area.&lt;/p&gt;
&lt;h2 id=&quot;inverting-the-model-and-leaking-through-gradients&quot;&gt;Inverting the model and leaking through gradients&lt;/h2&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/1906.08935&quot;&gt;Deep Leakage from Gradients&lt;/a&gt;, by Zhu, Liu and Han, NeurIPS 2019, is the paper that changed the conversation about federated learning: from the shared gradients, they rebuilt training images and text almost pixel by pixel.&lt;/p&gt;
&lt;p&gt;The ones that followed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/2309.13016&quot;&gt;Understanding Deep Gradient Leakage via Inversion Influence Functions&lt;/a&gt;, by Zhang and colleagues, NeurIPS 2023, gives a way to analyse leakage without running the attack&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://pmc.ncbi.nlm.nih.gov/articles/PMC10217429/&quot;&gt;Wasserstein Distance-Based Deep Leakage from Gradients&lt;/a&gt;, from 2023, changes the distance used in the reconstruction&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1186/s42400-024-00227-7&quot;&gt;Iterative and mixed-spaces image gradient inversion attack in federated learning&lt;/a&gt;, by Fang and colleagues, Cybersecurity 2024&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1145/3658644.3690292&quot;&gt;Uncovering Gradient Inversion Risks in Practical Language Model Training&lt;/a&gt;, by Feng and colleagues, CCS 2024, takes the attack to language model training&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://arxiv.org/abs/2410.21453&quot;&gt;Inverting Gradient Attacks Makes Powerful Data Poisoning&lt;/a&gt;, by Bouaziz and colleagues, 2024, uses inversion to poison training&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1007/978-3-031-30648-8_1&quot;&gt;A Survey of the Implementations of Model Inversion Attacks&lt;/a&gt;, by Song and Namiot, 2023&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;weights-as-an-attack-surface&quot;&gt;Weights as an attack surface&lt;/h2&gt;
&lt;p&gt;If the attacker gets the weights file, extraction ends there. Two sides of that interest me.&lt;/p&gt;
&lt;p&gt;The first is the format. &lt;a rel=&quot;external&quot; href=&quot;https://github.com/safetensors/safetensors&quot;&gt;safetensors&lt;/a&gt; exists because PyTorch&#39;s pickle format can execute code on load; safetensors stores only tensors. The &lt;a rel=&quot;external&quot; href=&quot;https://huggingface.co/blog/ngxson/common-ai-model-formats&quot;&gt;Hugging Face post on common formats&lt;/a&gt; compares safetensors, GGUF and others, and &lt;a rel=&quot;external&quot; href=&quot;https://github.com/justinchuby/onnx-safetensors&quot;&gt;onnx-safetensors&lt;/a&gt; connects ONNX to safetensors.&lt;/p&gt;
&lt;p&gt;The second is protecting the weights of frontier models. RAND&#39;s report &lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.7249/RRA2849-1&quot;&gt;Securing AI Model Weights&lt;/a&gt;, from 2024, organizes the attack vectors and the security levels needed against each kind of attacker.&lt;/p&gt;
&lt;h2 id=&quot;what-was-left-out&quot;&gt;What was left out&lt;/h2&gt;
&lt;p&gt;The items from the original list on distributed training and sharding (FSDP), checkpoints, serving in general and neural networks applied to detecting vulnerabilities were removed. They are good, but they are not about model extraction. Also removed: B3, which is about backdoors, a 2025 adversarial attack unrelated to extraction, and the link to Carlini&#39;s talk at Virginia Tech, which now returns 404.&lt;/p&gt;
</content>
        
    </entry>
</feed>
