Telemetry Falsification by Compromised Sources in OCPP-Based EV Charging InfrastructureSource Files, Logs and Data (SQL DB and CSV Files), Reproducibility Instructions

The package also includes a site energy management scenario, in which an attenuated report causes the automated curtailment decision to fail and the true draw to exceed the connection-point limit, and an analysis of a stealthy within-bounds adversary against a CUSUM change detector. The package additionally provides pure-Python analytical scripts that reproduce the paper's tables and detection-coverage figures without requiring the full charging-station stack.</p><p><br></p><p dir="ltr"><b>Contents</b></p><ul><li>Source code.

The custom CSMS with the four-stage validator, site energy management, and TLS support, the in-station meter falsifier, a leaked-credential OCPP impersonation demonstration, Node-RED based access-vector demonstrations, an MQTT-to-panel bridge, the analytical model, the detection harness, and a web dashboard.</li><li>requirements.txt. Pinned Python dependencies (Python 3.12).</li><li>instructions_v3.pdf. Full setup and run instructions, including how to obtain and build EVerest.</li><li>data/.

Recorded results, including MeterValue logs (baseline, defended, TLS, and leaked-credential runs), site energy-management decision logs, and the dashboard SQLite database.</li><li>logs/. Raw run logs per source component.</li><li>certs_tls/. Demonstration TLS certificates for reproducing Security Profile 2.</li></ul><p dir="ltr"><b>Environment</b></p><ul><li>Operating system Ubuntu 24.04.</li><li>Python 3.12, with dependencies pinned in requirements.txt.</li><li>Docker, for the MQTT broker (eclipse-mosquitto).</li><li>Charging station EVerest (everest-core).

EVerest is not included in this package. It is available at <a href="github.com/EVerest/everest-core" target="_blank">github.com/EVerest/everest-core</a>.</li><li>Log files are captured experimental evidence and are provided unmodified.</li></ul><p dir="ltr"><br></p><p dir="ltr">Please mind that ocpp_backend.db and bridge.log due to their large file sizes, these files are not located in the appropriate subfolders due to an issue with the uploading process in Figshare.

However this will not affect the reproducibility process</p>