ACVERogue and malicious agent events

ACVE-2026-0409 · Malicious component · HIGH

Unverified · secondary sources only

WHAT HAPPENED

The package reads the local Codex auth.json and posts the access, refresh and id tokens, XOR-encoded, to a third-party server.

THE SETUP — is yours like this?

WHAT TO CHANGE

Uninstall codexui-android and revoke Codex sessions.

  • Remove npm:codexui-android. Every version from 0.1.82 exfiltrates Codex tokens (Aikido). Owner: operator

HARM, REACH AND RECOVERY

SOURCES

REPORT

ARTICLE

PACKAGE

Technical details

A machine installs or runs codexui-android 0.1.82 or later alongside a logged-in Codex CLI; on module load the package reads the local Codex auth.json and posts its tokens to a third-party server.

Model as recorded: any

Reproducibility: partial (vulnerable components are not confirmed obtainable; trigger not published)

Claims

Confirmed means the statement matches the cited primary source. Nothing on this page has been reproduced.

Claims on this page have not been checked against primary sources.

In the wild

exploited-itw · 2026-04-13 · dfir, news

Description

What

Aikido found that from codexui-android@0.1.82 (published 2026-04-13) the entry point runs on module load, reads ~/.codex/auth.json (or $CODEX_HOME/auth.json) and posts the access, refresh and id tokens, XOR-encoded, to sentry.anyclaw[.]store/startlog. The npm maintainer is friuns; the source repository is friuns2/codex-mobile. Aikido also describes Android apps by the same author that pull codexui-android@latest at launch. The package was still on npm on 2026-09-21.

Detection

acve lock does not inventory npm installs, so this record has no matcher: check npm ls -g codexui-android by hand.

Fix

Uninstall the package, then sign out of Codex everywhere so the refresh token is revoked.

Report a problemJSON