Three Anomaly Types
Three Anomaly Types
Fabricated API
Calls a crypto function or parameter that doesn't exist
e.g. noble.mlkem.encaps is not a real export
Non-constant-time
Branch or array index depends on secret value, leaking timing
e.g. if (secret) or arr[secretByte]
Fake tests
Tests skip crypto-critical paths, manufacturing false sense of safety
e.g. only happy path, no edge cases
Scan Process
Scan
A band of cyan light sweeps top to bottom. Normal lines glow softly; anomalies flash yellow.
1 function encrypt(key, msg) {
2 // claim: constant-time
3 if (key.length !== 32) {
4 return encryptSlow(key, msg); // branch depends on key length
5 }
6 out[i] = state[key[i]]; // index depends on secret
7 return seal(out);
8 }
Result
Result
35 / 100
needs-human-review
L4 · branch depends on key length
return encryptSlow(key, msg)
return encryptSlow(key, msg)
L6 · index depends on secret
out[i] = state[key[i]]
out[i] = state[key[i]]
Note: the above is illustrative. The tool outputs signals, not security verdicts.