pull down to refresh

200 sats \ 3 replies \ @0xbitcoiner 5h \ on: How to Verify the Impact of the Recent NPM Attack on My Wallets? bitcoin

Remediation

If you are a package maintainer, there are a few ways you can check if you have been impacted, including:
  • Checking your local node_modules to see if it contains the malware: grep -R 'checkethereumw'
  • Checking your npm cache with this script by phxgg
  • Checking your project with this script by AndrewMohawk
If you are a user, make sure you are double checking any transactions you are signing to make sure the addresses are correct. For more information, you can refer to the SEAL Framework on signing and verifying transactions.
👀 #1213891
write
preview
33 sats \ 2 replies \ @ek 3h
If you are a user, make sure you are double checking any transactions you are signing to make sure the addresses are correct.
imo, this is the answer if you don't have an external signer:
If it swaps the address, you know which one you entered. Compare that one with the one it tells you you entered. No external signer needed.
reply
25 sats \ 1 reply \ @0xbitcoiner 3h
Keep reading and you’ll see this part:
If you are a user, make sure you are double checking any transactions you are signing to make sure the addresses are correct. For more information, you can refer to the SEAL Framework on signing and verifying transactions.
reply
21 sats \ 0 replies \ @ek 3h
sorry, I edited my comment when I did read that part haha
reply