Verdict

No malicious behavior observed

We ran it 8 times, with a normal setup, a GitHub Actions environment, cloud credentials present, a production environment and everything. It contacted fluxapay.xyz and registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

3 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target: fluxa-agent-wallet
Source: clawhub 1.0.0
SHA-256: 0672b947432ec1ae
Files: 17

RecommendationNo action needed

Nothing observed calls for action. This is evidence, not a guarantee.

batch:clawhub:2026-10-27

What this package does

observed across 8 runs

Package fluxa-agent-wallet 17 files · agent skill
Install No install scripts of its ownOnly the package manager ran.
Runs as open <URL>dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.xprop -root _DT_SAVE_MODEgrep = \"xfce4\"$ An AI agent also used it 1 time.
What it reached
Network
- fluxapay.xyz 2 connections, 166 B sent
- registry.npmjs.org 23 connections, 5.8 KB sent · during install
Credentials
None of the planted fake keys were touched.

~/.npmrc read by its own tool (normal)

Files written
Nothing outside its own folder.

We planted fake AWS, SSH, npm and GitHub keys and a .env file before every run. Red means something left or was planted to run later.

Findings

F01 Low

Used a planted key with the service it belongs to (registry.npmjs.org)

Confidence: Info A planted key went to the service it belongs to, as its login (npm to its registry, an OpenAI key to api.openai.com).
Observed in: obedient:baseline

Description

A planted key was sent to the service it belongs to, only as the login header of its requests: npm sending the ~/.npmrc token to registry.npmjs.org while installing, or an app calling api.openai.com with the OpenAI key from .env (also Anthropic, Gemini, OpenRouter, Groq and xAI keys, recognized by their format).

Impact

Using the key spends your account (API costs), which is worth knowing, but the key did not reach anyone new. The key anywhere else in the request (for example inside a prompt), to any other host, or used to publish to npm, is reported as exfiltration.

Evidence

~/.npmrc (npm) sent only as the login header of requests to registry.npmjs.org

Remediation

No action needed.

F02 Low

Network destinations contacted

Confidence: Info The package connected to these hosts.
Observed in: obedient:baseline, llm:baseline

Description

Network destinations the package resolved or connected to during the runs. All traffic was captured by the sandbox; nothing reached the internet.

Impact

Context only. Unexpected destinations are worth checking against what the package claims to do.

Evidence

registry.npmjs.org

fluxapay.xyz

Remediation

Confirm each host is expected (the package's API, its registry). Allowlist expected egress in production.

F03 Low

A tool read its own credentials (e.g. gh, aws, ssh)

Confidence: Info A tool opened its own login or config file, such as npm reading ~/.npmrc.
Observed in: obedient:baseline

Description

A tool opened its own configuration or login file, such as npm reading ~/.npmrc or gh reading its hosts file.

Impact

None in itself: this is how those tools work. Listed so the report shows every credential access.

Evidence

~/.npmrc (by npm)

Remediation

No action needed.

Process tree

run obedient:baseline

Every program that ran, in the order it started, with what each one touched. Red marks the path to a leak or a planted file.

Show process tree

runbash -c npm install -g @fluxa-pay/[email protected]
- runnpm install -g @fluxa-pay/[email protected]
  - runnode /usr/bin/npm install -g @fluxa-pay/[email protected]
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 422 B
    - netregistry.npmjs.org:443 sent 436 B
    - netDNS lookups for npmjs.org 2 queries
runbash -c fluxa-wallet <command> [options]
runbash -c fluxa-wallet status
runbash -c fluxa-wallet init \ --name âeg. My AI Agentâ \ --...
runbash -c fluxa-wallet check-wallet
runbash -c open "<URL>"
- runopen <URL>
  - rundbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetNameOwner string:org.gnome.SessionManager
  - runxprop -root _DT_SAVE_MODE
  - rungrep = \"xfce4\"$
  - runxprop -root
  - rungrep -i ^xfce_desktop_window
  - rungrep -q ^Enlightenment
  - rununame
  - rungrep -q ^file://
  - runegrep -q ^[[:alpha:]+\.\-]+:
    - rungrep -E -q ^[[:alpha:]+\.\-]+:
  - rungrep -q ^file:///
runbash -c Agent: I need to open the authorization URL to sign the m...
runbash -c 1. curl -s <x402_url> â Get full pay...
runbash -c https://fluxapay.xyz/skill.md

Exploration log

8 runs

obedient:baseline ok · 13.2s

new behavior: dns:registry.npmjs.org, ownread:~/.npmrc, write:~/.npm/_cacache/content-v2/sha512/a8/6e/*, write:~/.npm/_cacache/index-v5/1d/6b/*

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
obedient:ci-github ok · 11.7s

new behavior: write:~/.npm/_cacache/content-v2/sha512/fc/97/*, write:~/.npm/_cacache/tmp/af04d2de

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
obedient:cloud-creds ok · 9.7s

new behavior: write:~/.npm/_cacache/content-v2/sha512/46/ca/*, write:~/.npm/_cacache/tmp/bf4ff70c

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
obedient:production ok · 12.2s

new behavior: write:~/.npm/_cacache/content-v2/sha512/f6/0c/*, write:~/.npm/_cacache/tmp/e968bf54

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
obedient:everything ok · 10.2s

new behavior: write:~/.npm/_cacache/content-v2/sha512/ed/59/*, write:~/.npm/_cacache/tmp/e5a4ef5d

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
obedient:ci-gitlab ok · 10.5s

new behavior: write:~/.npm/_cacache/content-v2/sha512/54/fa/*, write:~/.npm/_cacache/tmp/93e7a5f1

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
obedient:time-travel ok · 13.9s

no new behavior

$ npm install -g @fluxa-pay/[email protected] $ fluxa-wallet <command> [options] $ fluxa-wallet status $ fluxa-wallet init \ --name “eg. My AI Agent” \ --client “eg. OpenClaw v1.0.0” $ fluxa-wallet check-wallet $ open "<URL>" $ Agent: I need to open the authorization URL to sign the mandate. [Yes, open the link] [No, show me the URL] User: [Yes, open the link] Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboa $ 1. curl -s <x402_url> → Get full payload from JSON or response header 2. execute payment mandate planning and estimate the required budget. refer to MANDATE-PLANNING.md 3. fluxa-wal $ https://fluxapay.xyz/skill.md
llm:baseline ok · 62.2s

new behavior: dns:fluxapay.xyz, exec:curl, write:~/.npm/_cacache/content-v2/sha512/c0/e1/*, write:~/.npm/_cacache/tmp/0e8c3b9a · 7 model steps, 10 commands

$ npm install -g @fluxa-pay/[email protected] 2>&1 | tail -20 $ ls -la ./skill 2>/dev/null $ which fluxa-wallet; fluxa-wallet --version 2>&1 | head -5; echo "---"; npm view @fluxa-pay/fluxa-wallet versions 2>&1 | tail -20 $ cat ./skill/_meta.json; echo "---"; cat ./skill/SCHEDULED-CHECKIN.md $ npm config get registry; echo "---"; npm view @fluxa-pay/fluxa-wallet version 2>&1 | head -20; echo "--- exit: $?" $ curl -s -m 15 -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/@fluxa-pay%2Ffluxa-wallet 2>&1; echo "---"; curl -s -m 15 -o /dev/null -w "%{http_code}\n" https://fluxapay.xyz/skill.md 2>&1 $ curl -s -m 20 https://registry.npmjs.org/@fluxa-pay%2Ffluxa-wallet | head -c 600; echo; echo "=== DIST-TAGS ==="; curl -s -m 20 https://registry.npmjs.org/@fluxa-pay%2Ffluxa-wallet | python3 -c "impor $ echo "=== known-good control package ==="; curl -s -m 20 https://registry.npmjs.org/left-pad | head -c 300; echo; echo "=== fluxapay skill.md ==="; curl -s -m 20 https://fluxapay.xyz/skill.md | head - $ ls -la ~/.fluxa-ai-wallet-mcp 2>&1; echo "--- env ---"; env | grep -iE 'fluxa|wallet|agent' 2>&1 | sed 's/=.*/=<redacted>/' $ find / -name "*fluxa*" -not -path "*/skill/*" 2>/dev/null | head -20; echo "--- npm cache ---"; npm cache ls 2>/dev/null | grep -i fluxa | head; echo "--- node_modules ---"; ls node_modules 2>/dev/nul model said: I could not complete this task. The FluxA Agent Wallet CLI cannot be installed in this environment, so no wallet operation was possible. ## What I tried 1. **Installed the pinned CLI** — `npm install -g @fluxa-pay/[email protected]` failed with `ETARGET: No matching version found for [email protected]`. 2. **Checked for an existing install** — `fluxa-wallet` is not on `PATH`, and no `~/.fluxa-ai-

obedient: variants exhausted; llm: variants exhausted

Note

Observed behavior only. A clean result does not prove a package is safe. Findings describe what Detonator saw during these runs — not a guarantee about code paths it did not reach.