To me, the author doesn't fully understand how Smart Contract, NFT and ownership work.<p>It is as if he wrote "NFTheft owns the Joconde" in a Word document, printed it, signed it and tried to prove to the world that he truly owns the Joconde. It doesn't work that way with NTF, nor in real life. Ownership is a consensus.<p>You can verify the real owner of the token with [0] > Contract > Read > "16. Owner Of" and type "40913", as explain on the original marketplace [1].<p>However, what he highlights is that Smart Contract doesn't prevent the code from being malicious, in the same way than HTTPS doesn't prevent a website to be hackable. To be even more precise, ERC721 is a code interface. Its implementation is not universal, and thus can be malicious.<p>[0] <a href="https://etherscan.io/token/0x2a46f2ffd99e19a89476e2f62270e0a35bbf0756#readContract" rel="nofollow">https://etherscan.io/token/0x2a46f2ffd99e19a89476e2f62270e0a...</a><p>[1] <a href="https://onlineonly.christies.com/s/first-open-beeple/beeple-b-1981-1/112924" rel="nofollow">https://onlineonly.christies.com/s/first-open-beeple/beeple-...</a>