transaction malleability "attack" vectors are any of the following transaction malleability "attack" vectors currently feasible?

alter scriptsig from:

OP_PUSHDATA &lt;sig&gt; OP_PUSHDATA &lt;pubkey&gt;


to one of:

1) OP_1 OP_SHA1 OP_DROP OP_PUSHDATA &lt;sig&gt; OP_PUSHDATA &lt;pubkey&gt;
2) OP_PUSHDATA &lt;sig&gt; OP_PUSHDATA &lt;pubkey&gt; OP_1 OP_SHA1 OP_DROP
3) OP_PUSHDATA &lt;sig&gt; OP_PUSHDATA &lt;pubkey&gt; OP_NOP


so that the corresponding scriptpubkey still evaluates to true:

OP_DUP OP_HASH160 OP_PUSHDATA &lt;address&gt; OP_EQUALVERIFY OP_CHECKSIG


i can't tell if this is handled by point 6 in bip 62 or not:


  
  Superfluous scriptSig operations Adding extra data pushes at the start of scripts, which are not consumed by the corresponding
  scriptPubKey, is also a source of malleability.
  


judging by the code it looks like it has been taken care of, but my c++ knowledge is not great...
Point (6) does not eliminate this source of malleability. Rather, point (2) of BIP62 disallows all three modifications you suggested. BIP62 describes the problem:


  Non-push operations in scriptSig Any sequence of script operations in scriptSig that results in the intended data pushes, but is not just a push of that data, results in an alternative transaction with the same validity.


And the proposed solution:


  Non-push operations in scriptSig Only data pushes are allowed in scriptSig. Evaluating any other operation makes the script evaluate to false. See reference: Push operators.