F-2025-0001·credential-exposure

Private key in plain sight in .env

Fixedrafflelotteryvrf
TL;DR

Sensitive API keys and private keys were stored in environment files committed to version control, exposing critical secrets to anyone with repository access.

Severity
CRITICAL
Impact
HIGH
Likelihood
HIGH
Method
MManual review
CAT.
Complexity
LOW
Exploitability
HIGH
02Section · Description

Description

Sensitive information, including API keys and private keys, was found stored directly in environment variables. Such files (e.g., .env) must never be committed to version control as this exposes critical secrets to potential compromise.

03Section · Impact

Impact

A malicious actor could retrieve the exposed private keys and use them to steal associated funds or access protected services.

04Section · Recommendation

Recommendation

All keys (both private and API) should be rotated immediately to invalidate any potentially exposed credentials. Additionally, include the .env file in .gitignore to prevent it from being pushed to the repository in the future.

05Section · Resolution

Resolution

Nexalo: Fixed.

Zealynx: Private keys removed.

Status
Fixed
F-2025-0001

oog
zealynx

Smart Contract Security Digest

Monthly exploit breakdowns, audit checklists, and DeFi security research — straight to your inbox

© 2026 Zealynx