Changelog

Node.js SDK 1.1.0: the kill switch holds when the clock moves

RSS feedSystem status

All changes

October 2026

  1. Security

    pwfauth 1.1.0 on npm makes the kill switch hold when someone moves the PC clock, refuses a plain "success" from a proxy and repairs a wrong clock by itself. Update with npm install pwfauth

    • The kill switch can no longer be dodged by moving the clock. Only an encrypted reply counts as an answer, and maxHeartbeatFailures beats in a row without one end the session with NETWORK_LOST, or CLOCK_SKEW when every refusal blamed the clock. HTTP 429 has its own budget, maxRateLimitedBeats (10)
    • A plain {"success": true} from a proxy, a hosts-file redirect or a fake server now rejects with PwfSecurityError. In 1.0.0 it signed the user in
    • A wrong system clock repairs itself: the client shifts by the server's time and sends the request once more. autoCorrectClock: false turns it off
    • resetHardwareId(licenseKey, reason) moves a license to a new PC at once, within the app's switch and cooldown (12 hours by default)
    • registerAccountWithKey() and redeemKey() for accounts that run on license keys, and PwfErrorCodes gains the codes for moves and accounts
    • Every request sends User-Agent: pwfauth-node/1.1.0 (+https://pwfauth.com), and a request that never reached the server now says "Cannot reach the license server" instead of reporting a timeout

    Node.js SDK guide