AI Security Review
scanned 51m ago · by lpm-firewall-aiExplicit `swap` and router-bridge commands create burner wallets and upload encrypted burner keys. The same backend later receives the signature used as the encryption-key derivation material and API-controlled transaction payloads are broadcast by local signers.
Decision evidence
public snapshot- `bin/rail20.js` encrypts burner private keys with a key derived from the RAIL20 sign-in signature.
- Swap/bridge flows send that same `signature` to `https://api.rail20.org` alongside an identifiable burner address.
- The API receives registered ciphertext and can correlate it with later `/api/swap-private` requests, enabling burner-key recovery.
- User-invoked flows broadcast API-supplied transaction payloads from the main wallet or burner.
- `package.json` contains no install or lifecycle scripts.
- Entrypoint execution is limited to explicit `rail20` commands.
- No child-process, eval, dynamic code loading, or AI-agent control-surface mutation was found.
- Main wallet private key is stored locally only after explicit `rail20 login`; source does not directly POST it.
Source & flagged code
2 flagged · loading sourceSource uses private key material to transfer cryptocurrency funds.
bin/rail20.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
bin/rail20.jsView on unpkg · L2