Skip to content
ARTEX.sh

ARTEX's browser extension:what it captures, and what defenders should check.

A viral post on X in November 2026 said ARTEX ships a browser extension that hands a live login session to its AI. This site checked the public repositories. One maintained fork, BaaRai/ARTEX, does include such an extension. This page explains what its own code and docs say it does, which copies have it, and what defenders can do about session reuse. It gives no setup steps.

Checked

The claim, and what the code shows

On 2026-11-12 the X account @mingzi206 posted in Chinese that ARTEX has a dedicated browser extension that syncs a real browser's cookies and tokens to the agent, so the AI can test behind login and two-factor sign-in. It is a single user post, and it links to the BaaRai/ARTEX fork.

The repositories confirm part of it. BaaRai/ARTEX added an extension/ folder on 2026-10-11. Its README says the extension is for authenticated targets: you log in once, including captcha, email codes and 2FA, capture the session, and the requests and responses land in ARTEX's traffic store. The original ARTEX code, the RuoJi6/ARTEX line and the other tracked forks have no such folder, except one derivative of BaaRai (below).

What the extension does

The extension is called ARTEX Traffic Capture. Its manifest is a Chrome and Edge Manifest V3 extension that asks for the debugger, storage and tabs permissions on all sites. Its code uses the browser's debugger network events on one chosen tab and sends text request and response pairs, with their headers and bodies, to the ARTEX server in batches. Binary bodies are skipped and bodies are cut at 256 KiB.

The commit that added it says the reason: ARTEX's recording proxy only sees the agent's own traffic, so anything behind a human gate such as a captcha, an email code, 2FA or single sign-on stayed dark. The operator's browser becomes a second capture source. The same fork lets an operator replay a recorded request, with its headers, from the traffic view.

It does not ask for the browser's cookies permission. What it records is what the debugger reports for that tab's requests, which can include session tokens sent in request headers. A fix on 2026-11-16 says that before it, capture silently recorded nothing because of a header parsing bug.

Which forks have it

Checked on 2026-11-18 against every fork this site tracks.

CopyExtensionNotes
BaaRai/ARTEXYes, since 2026-10-11In release v0.4.0 and later. Header fix on 2026-11-16, after v0.6.0.
Adyanming/ARTEX-ProYesDerived from BaaRai's English ARTEX.
RuoJi6/ARTEX and other tracked forksNoNo extension folder in the repository.
Original ARTEX v0.3.15NoNot part of the original code.

Why it matters for defenders

Login pages, captchas and 2FA slow down automated attacks. A tool that works from a real logged-in browser moves past them, because the session already exists. For authorized testers that is the point: it lets them test the parts of an app behind login.

For defenders the lesson is the same as with any stolen session. Microsoft notes in its ARTEX secrets research that tokens already issued stay valid until they expire. If an attacker gets a session through a phished user, a compromised laptop or an insider, a capture tool like this one makes that session easier to use at machine speed.

What to set and what to watch

These are general session protections. They apply to any tool that reuses a logged-in session, not only this extension.

  1. 01

    Keep sessions short

    Limit session and token lifetimes, especially for admin and staff apps, and end idle sessions.

  2. 02

    Bind tokens to the client

    Where your platform supports it, bind sessions to a device or certificate so a copied token does not work elsewhere.

  3. 03

    Ask again before sensitive actions

    Require a fresh sign-in or second factor before exports, payouts, permission changes and bulk lookups. A reused session should not be enough.

  4. 04

    Watch for session reuse

    Alert when one session shows up from a new IP, network or user agent, or suddenly makes far more requests than a person would. The FBI also advises alerts on sequential lookups and unusually many records per session.

  5. 05

    Know which logs to check

    Keep sign-in logs, session or token IDs per request, source IP and user agent in your app and identity logs. Being able to trace one session across requests is what lets you spot reuse.

  6. 06

    Revoke sessions in an incident

    Resetting a password is not enough if old sessions stay valid. Revoke sessions and tokens as part of your response (Microsoft).

Questions

Does every ARTEX copy have a browser extension?
No. On 2026-11-18 only BaaRai/ARTEX and one derivative of it had the extension folder. The original code and RuoJi6/ARTEX do not.
Does the extension steal cookies?
It records the traffic of one tab its operator chooses and sends it to that operator's ARTEX server. It does not request the browser's cookies permission.
Can 2FA stop this?
2FA protects the login, not a session that already exists. Short sessions, token binding and a new check before sensitive actions help more here.

Sources

Every claim on this page comes from these sources or from this site's own sourced pages. Open them for the full reports.

Follow the ARTEX story.

New forks, releases and reports, dated and sourced.

Isometric plane with glowing light columns