If you’re using direct pin manipulation via the Blynk app (rather than using virtual pins) then the pins going low on boot-up of your MCU is intentional behaviour of the Blynk library. It’s discussed in detail in this thread:
If that behaviour isn’t acceptable then the simple workaround is to use virtual pins (which is the most sensible approach anyway).