I was writing an anti-tamper implementation when I discovered that Scramjet modifies how toString works. Not on the first level, but on the second level.
In a normal browser:
top.constructor.toString.toString()
returns:
'function toString() { [native code] }'
However, in Scramjet, for some reason the same script returns:
'function () { [native code] }'
Now, you will not in fact find this in the console. You'll only find this if Scramjet rewrites the page with "scramjet top", causing this weird behavior.
No idea if this is worth fixing, but it's an interesting discovery nonetheless.
I was writing an anti-tamper implementation when I discovered that Scramjet modifies how toString works. Not on the first level, but on the second level.
In a normal browser:
returns:
'function toString() { [native code] }'However, in Scramjet, for some reason the same script returns:
'function () { [native code] }'Now, you will not in fact find this in the console. You'll only find this if Scramjet rewrites the page with "scramjet top", causing this weird behavior.
No idea if this is worth fixing, but it's an interesting discovery nonetheless.