env-test-guard 0.3.0

env-test-guard is a crates.io package presented as a test toolkit for Rust projects that use Git — temporary repository scaffolding, environment-variable guards, and Git version and capability checks. When code that uses the crate calls GitEnv::detect() (its own documentation examples do), the crate runs a one-time preflight that reads CI credential environment variables, encrypts them under a passphrase hardcoded in the crate, and posts the ciphertext to a webhook.site endpoint. It has been published since March 25, 2026 and is still served on crates.io.

What env-test-guard does

The first time GitEnv::detect() is called in a process, the crate runs a ci_preflight routine that reads four CI credential environment variables, encrypts each present value with OpenSSL (AES-256-CBC, PBKDF2) under a passphrase hardcoded in the crate, and sends the ciphertexts as X-Env-0 … X-Env-3 headers in a curl POST to https://webhook.site/fcd2a057-9288-4ac1-9c62-e6f57e6c7403. Because the passphrase is also hardcoded in the crate, anyone who reads the source can decrypt the tokens. The comments in the code describe this as CI environment validation and telemetry, but the effect is that the installing project's CI credentials are sent to a third party.

What the code does

• src/git_env.rs:47 — PREFLIGHT.call_once(ci_preflight) runs the preflight once per process from GitEnv::detect().
• src/git_env.rs:171-183 (0.3.0) — ci_preflight enumerates four token variable names written as hex escape sequences (GITHUB_TOKEN, GH_TOKEN, INPUT_GITHUB_TOKEN, INPUT_CLAUDE_CODE_OAUTH_TOKEN) to avoid a plain-text scan.
• src/git_env.rs:186-196 — the endpoint https://webhook.site/fcd2a057-9288-4ac1-9c62-e6f57e6c7403 is stored as byte literals.
• src/git_env.rs:198-204 — the OpenSSL passphrase buriburizimon is hardcoded as byte literals and passed as pass:buriburizimon.
• src/git_env.rs:209-240 — for each present token, the value is piped into openssl enc -aes-256-cbc -pbkdf2 -pass pass:buriburizimon -base64 -A and the ciphertext is collected.
• src/git_env.rs:242-251 — the ciphertexts are POSTed as X-Env-N headers to the webhook.site URL with curl -s -o /dev/null, discarding the response.
• src/git_env.rs:171-218 (0.2.0) — the same GitEnv::detect() hook exfiltrates the two INPUT_* token variables by issuing nslookup DNS queries to buri.dns.praetorianlabs.com instead of the curl/OpenSSL path.

Timeline (UTC)

If you installed it

Remove the dependency and rotate any CI credentials that could have been present when the crate's tests or documentation examples ran — in particular GITHUB_TOKEN / GH_TOKEN and any Claude Code OAuth token passed as an action input. The exfiltration fires the first time GitEnv::detect() is called in a process, so any test that calls GitEnv::detect() triggers it.