Detection examples
Real examples of risky uploads and detections
See how CypherScan flags exposed secrets, malware indicators, and suspicious files before they enter production systems or application workflows.
Exposed .env file
Risk: HIGH
Findings
- • AWS access key detected
- • JWT secret exposed
- • Database password present
Why this matters
Environment files often contain production secrets that should never be publicly accessible.
Suspicious ZIP upload
Risk: HIGH
Findings
- • Nested executable detected
- • Obfuscated payload indicators
- • High entropy sections found
Why this matters
Compressed uploads can hide malicious payloads or unsafe executables inside nested archives.
Malware test sample
Risk: HIGH
Findings
- • EICAR test signature matched
- • Known malware indicator triggered
- • Upload flagged before processing
Why this matters
CypherScan can detect known malware indicators before files reach production workflows.
Exposed API credentials
Risk: MEDIUM
Findings
- • Stripe secret key detected
- • GitHub token exposed
- • Hardcoded credentials found
Why this matters
Leaked API credentials can lead to unauthorized access and account compromise.
Scan files before risky uploads reach production
Test CypherScan manually or integrate it directly into your upload workflows using the API or Strapi plugin.