Source inspection found no install hook or confirmed attack behavior. The reported dynamic execution is schema-validator code generation, the policy dependency loads a local WebAssembly module, and custom provider keys require an explicitly supplied HTTPS endpoint.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the oxagen CLI or a command that uses its policy and registry features.
Impact
No confirmed unauthorized credential transfer, remote payload execution, or install-time mutation was established.
Mechanism
The CLI dispatches on supplied arguments, loads local Cedar WebAssembly bindings, and fetches registry data for digest checks. Custom provider credentials require the user to supply an HTTPS endpoint.
Evidence
package.jsonoxagen.mjs.lpm-dependency-evidence-57f95135-321f-4bcd-baf-7060f5d3c67e/0/npm-linux/package.json.lpm-dependency-evidence-57f95135-321f-4bcd-baf-7060f5d3c67e/0/npm-linux/esm/cedar_wasm.js