Security

What to expect

NestBox is built for a home or office network. Its HTTP API has no accounts or keys: anything that can reach the device on the LAN can make the pet react, put text on its screen, or read what it is doing (GET /v1/state). Don't expose it to the internet or forward a port to it.

What the device does refuse:

• Requests whose Host is not one of its own names or addresses (403), so a web page can't reach it through DNS rebinding.
• Writes from another site's page (an Origin that isn't the device's own, including null).
• Events that only the device itself may send (its button, the USB host's sleep, dismissing what waits) when they come from the network.
• Bodies over 16 KB (413).

During Wi-Fi setup the device runs its own access point with a new 8-character password each time, shown only on its screen. The home network's password is stored on the device; no request returns it.

The Mac companion sends key-press counts, idle time, CPU load and the screen-lock state, never which keys. The Claude Code hook sends file names and program names, never prompts, command lines, paths or file contents (integrations/claude-code).

Reporting a vulnerability

Email security@nestbox.pet with what you found and how to reproduce it, rather than opening a public issue.