<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Red Team on @Unc1e</title>
    <link>https://www.unc.la/en/tags/red-team/</link>
    <description>Recent content in Red Team on @Unc1e</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:20:00 +0800</lastBuildDate>
    <atom:link href="https://www.unc.la/en/tags/red-team/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>You Bought the Hands, Not the Brain: After Analyzing Burp AT, I Built an Open-Source Burp MCP</title>
      <link>https://www.unc.la/en/posts/penetration/burp-at-brain-hand-open-source-mcp/</link>
      <pubDate>Wed, 12 Aug 2026 00:20:00 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/burp-at-brain-hand-open-source-mcp/</guid>
      <description>Burp AT proves that penetration testing can be handed to AI, but it locks the model in the cloud and suffers from approval fatigue in production. I analyzed its protocol, followed the official front door, and built an open-source burp-mcp-server — filling the gaps that make or break a red-team automation loop.</description>
    </item>
    <item>
      <title>Agents Can Now Take Action—Security Can&#39;t Stay in the Conversation: Runtime Design at the Action Boundary</title>
      <link>https://www.unc.la/en/posts/penetration/agents-next-problem-is-action-boundary/</link>
      <pubDate>Sun, 02 Aug 2026 10:50:39 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/agents-next-problem-is-action-boundary/</guid>
      <description>&lt;p&gt;Lately I&amp;rsquo;ve been doing more and more AI red teaming: half the time thinking about how to attack Agents, and the other half thinking about:&lt;/p&gt;
&lt;p&gt;once the attacks are done, what should real-world defense actually look like?&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve written a local-first Agent Runtime Guard (ARG) myself, and I&amp;rsquo;ve also taken apart Microsoft&amp;rsquo;s newly open-sourced Agent Governance Toolkit (AGT). After taking both apart, the conclusion is actually quite clear:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Agent runtime protection is, in essence, the &amp;ldquo;firewall&amp;rdquo; of the LLM era&lt;/strong&gt;. Whenever I mention &amp;ldquo;firewall&amp;rdquo;—a word that has been beaten to death—I want to laugh. Still, this is decidedly not another layer of prompt rhetoric, nor is it old IAM renamed. What it intercepts is the segment where &amp;ldquo;the model&amp;rsquo;s intent has already formed, but the side effects haven&amp;rsquo;t happened yet&amp;rdquo;—the command hasn&amp;rsquo;t been exec&amp;rsquo;d, the keys haven&amp;rsquo;t been read, the email hasn&amp;rsquo;t been sent, no HTTP has left the network.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reverse OpenRouter</title>
      <link>https://www.unc.la/en/posts/penetration/iy7k17ehlduoblsm/</link>
      <pubDate>Sun, 26 Apr 2026 12:10:14 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/iy7k17ehlduoblsm/</guid>
      <description>&lt;p&gt;Reverse-proxy the OpenRouter AI API through an overseas server to work around regional access restrictions.&lt;/p&gt;
&lt;h2 id=&#34;background-scqa&#34;&gt;Background (SCQA)&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;S - Situation&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Overseas AI services (image generation, chat, etc.) are typically accessed through aggregator platforms like OpenRouter that offer a unified API, compatible with the OpenAI SDK.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;C - Complication&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;These services impose access restrictions on mainland China — if the requesting source IP is identified as originating from within China, service is refused outright.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stuffing OpenAI&#39;s Privacy Filter Model into the Red Team Toolchain</title>
      <link>https://www.unc.la/en/posts/penetration/openai-privacyfilter-into-redteam/</link>
      <pubDate>Sat, 25 Apr 2026 11:11:28 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/openai-privacyfilter-into-redteam/</guid>
      <description>&lt;p&gt;&lt;img loading=&#34;lazy&#34; referrerpolicy=&#34;no-referrer&#34; src=&#34;https://cdn.nlark.com/yuque/0/2026/png/166008/1777302701535-625c20f6-3b1b-4d69-8060-c6cfaca61d29.png&#34;&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Red team security tooling — rebuilding OpenAI&amp;rsquo;s Privacy Filter into an HTTP gateway for structured PII&lt;/p&gt;
&lt;p&gt;extraction&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;OpenAI open-sourced a small model called Privacy Filter that can identify PII such as names, emails, phone numbers, and addresses from unstructured text.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; referrerpolicy=&#34;no-referrer&#34; src=&#34;https://cdn.nlark.com/yuque/0/2026/png/166008/1777301197503-5cec4ca4-265a-4705-82b4-c2ca7e2d84e0.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;I spent one evening turning it into an HTTP gateway service, running on an NVIDIA L20, with dual-process inference peaking at 81 RPS and GPU utilization pushed to 98%.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Red Team Essential! Frp Anti-Traceability Enhanced Build</title>
      <link>https://www.unc.la/en/posts/penetration/np5v8tglxw95ztmk/</link>
      <pubDate>Mon, 14 Apr 2025 21:03:41 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/np5v8tglxw95ztmk/</guid>
      <description>&lt;p&gt;frp is a great tool — high performance, stable, and worth using.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; referrerpolicy=&#34;no-referrer&#34; src=&#34;https://cdn.nlark.com/yuque/0/2025/png/166008/1744648570174-90104017-d254-443e-82bf-fbcaec371323.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;However, its configuration file has gone through two format generations (&lt;code&gt;.ini&lt;/code&gt; -&amp;gt;&lt;code&gt;.toml&lt;/code&gt;), and the options can be somewhat complicated for newcomers.&lt;/p&gt;
&lt;p&gt;When project timelines are tight and workloads heavy, you may not have time to figure out what all these options mean in a short period.&lt;/p&gt;
&lt;p&gt;Hence this article — written on April 14, 2025; the currently applicable frp version is: &lt;a href=&#34;https://github.com/fatedier/frp/releases/tag/v0.61.2&#34;&gt;https://github.com/fatedier/frp/releases/tag/v0.61.2&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stable Packet Capture: Intercepting Traffic from Various Devices via a Transparent Proxy (mitmproxy Usage)</title>
      <link>https://www.unc.la/en/posts/penetration/lsqvp3qo4b2z8ro6/</link>
      <pubDate>Fri, 24 Nov 2023 23:20:13 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/lsqvp3qo4b2z8ro6/</guid>
      <description>&lt;p&gt;Tutorial reference&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://blog.csdn.net/zhuxian1277/article/details/111875951&#34;&gt;https://blog.csdn.net/zhuxian1277/article/details/111875951&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;use-case&#34;&gt;Use Case&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt;mitmproxy&lt;/font&gt;&lt;/strong&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt; is a powerful man-in-the-middle proxy tool that lets you intercept, view, and modify traffic between clients and servers. Its transparent proxy mode makes mitmproxy extremely useful in specific scenarios, especially when network traffic needs to be analyzed or tested without changing any settings on the target device.&lt;/font&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt;No proxy configuration needed&lt;/font&gt;&lt;/strong&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt;: Unlike Burp Suite, mitmproxy in transparent mode does not require manually setting an HTTP or HTTPS proxy on the target machine. This means the end user or test subject will not notice the proxy&amp;rsquo;s presence, reducing the chance of human intervention.&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt;Certificate installation&lt;/font&gt;&lt;/strong&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt;: Although no proxy configuration is required in transparent mode, to intercept and decrypt HTTPS traffic you still need to install mitmproxy&amp;rsquo;s root certificate on the target machine. This is similar to Burp Suite, since both must handle the SSL/TLS handshake to view encrypted traffic.&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font style=&#34;color:rgb(44, 44, 54);&#34;&gt;Via MitmWeb, you can view captured packets locally; in terms of usage it is not much different from Burp.&lt;/font&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img alt=&#34;mitmweb&#34; loading=&#34;lazy&#34; referrerpolicy=&#34;no-referrer&#34; src=&#34;https://cdn.nlark.com/yuque/0/2024/png/166008/1734491587977-7e5e72eb-8876-42f3-9d76-c20ff914b72d.png&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Obtain Source Code During Penetration Testing</title>
      <link>https://www.unc.la/en/posts/penetration/source_code_auditing_in_the_wild/</link>
      <pubDate>Tue, 31 Aug 2021 22:14:19 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/source_code_auditing_in_the_wild/</guid>
      <description>&lt;p&gt;Using a recent case, let&amp;rsquo;s talk about some techniques for obtaining source code in real engagements.&lt;/p&gt;
&lt;p&gt;(This is also material from a closed-door sharing session a while back: &lt;code&gt;hope you guys enjoy it~&lt;/code&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h1 id=&#34;liquid-files&#34;&gt;Liquid Files&lt;/h1&gt;
&lt;p&gt;Liquid Files is a foreign file-sharing (cloud disk) system; official site: &lt;a href=&#34;https://www.liquidfiles.com/&#34;&gt;https://www.liquidfiles.com/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; referrerpolicy=&#34;no-referrer&#34; src=&#34;https://cdn.nlark.com/yuque/0/2021/png/166008/1630069686727-4a2128c6-a2d4-4440-8e16-7f1322a82d99.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s a commercial system, widely used abroad.&lt;/p&gt;
&lt;p&gt;Today we&amp;rsquo;ll try to obtain the source code of this system and conduct a preliminary attack-surface assessment (an initial code audit).&lt;/p&gt;</description>
    </item>
    <item>
      <title>[Guest Post] A Commissioned Product Security Test</title>
      <link>https://www.unc.la/en/posts/penetration/fuxqaa/</link>
      <pubDate>Thu, 29 Oct 2020 23:06:59 +0800</pubDate>
      <guid>https://www.unc.la/en/posts/penetration/fuxqaa/</guid>
      <description>&lt;p&gt;This article was contributed to the Alibaba Cloud &lt;a href=&#34;https://xz.aliyun.com/&#34;&gt;Xianzhi Community&lt;/a&gt;. Original content; please cite the source when reposting.&lt;/p&gt;
&lt;h1 id=&#34;foreword&#34;&gt;Foreword&lt;/h1&gt;
&lt;p&gt;On an utterly unremarkable weekend, a buddy of mine messaged me saying he had a product security test on his hands that he couldn&amp;rsquo;t handle and asked me to help out. I wasn&amp;rsquo;t keen at first—but Haidilao hotpot is just too good, and so began this commissioned product security test.&lt;/p&gt;
&lt;p&gt;Product security testing means using limited resources (time/energy), through security testing and code audit among other means, to uncover as many vulnerabilities as possible, and to leverage these individual findings to drive the developers to fix the product&amp;rsquo;s security issues.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
