So, if I make a copy of a database with user names and passwords, then set the bits of the database to all zeroes on the server; it's theft? Because I now moved a "painting" from one area of space to another?
The thing is, the original state was reconstructed somewhere else without the permission of the property owner (the one/ones who arranged the original state), and that's what theft is. It's the same as moving a painting (a collection of state) to another region of space, but it's not easy to replicate a painting, so it gets exclusivity as well, but it's still the same concept; one thing appearing somewhere else in space.
The less obvious part is that you always HAVE to destroy (change) some other region of space in order to replicate the state you want a copy of, but you don't have to destroy the state in the source space. Due to the ease at which one can copy state within the realm of digital computers, the default behavior is to leave the state in tact, or you may not even have access to modify the source space.
As with the painting; less energy is required to move the state from one location in space to another, compared to replicating the state. This naturally adds exclusivity to the state, but still, you did not have permission to move the state, and that's what you are doing when you copy; you move state (not in a cut/paste manner) from one region of space to another.