-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected reserved word 'await' #285
Comments
@TheGreyRaven I would probably start by seeing if bumping to the latest version of @j4k0xb 's If it does, then the version in If not and the issue is still present there, then it's probably worth opening an upstream issue and providing an ideally minimal example of the code to reproduce the error: If not, but it works upstream, then providing an ideally minimal example of the code to reproduce the error here would make the most sense I think. |
Ah I see, I tested pasting the obfuscated code into their online ide and there it deobuscated most of the code just fine. |
This project currently seems to be using Line 62 in f6a2190
Latest @TheGreyRaven If you feel like doing a little more digging, it would be useful to know if you get the same error running |
I remember a similar discussion regarding the version in this repo Since it works fine the first time I assume the generated code get's corrupted at some point. |
You can use |
With overriding to latest webcrack, I still see this |
@VivaLaPanda Thanks for checking.
@TheGreyRaven / @VivaLaPanda Since it sounds like the issue is in |
this seems to fix it: although, i am skipping the problem instead of dealing with it. |
This seems to create a plugin that logs a const syntaxErrorPlugin: PluginItem = {
visitor: {
Program(path) {
// Example: this would log an error and allow Babel to continue parsing
console.error("Syntax error encountered. skipping", path);
path.skip();
}
}
}; Which is then added at the end of @fosteman Can you explain how this fixes the issue? From my quick / naive read.. this looks like it would just skip running any processing against the code at all; so while yes, it would technically skip the issue, I believe it would also skip doing anything at all wouldn't it? Do you have a code sample where this issue was natively occurring? I would like someone to be able to provide a real-world sample so we can actually debug this issue properly and see exactly where/why it's occurring. Edit: Resurrecting the stack trace from your edit: Stack Trace
We can see this part of the error, showing the code that caused it:
Putting the whole stack trace into ChatGPT 4o gave the following suggestion about the root cause of the error:
|
@TheGreyRaven The surrounding context in your error is less clear than what I discovered above in #285 (comment), but I suspect it's the same root cause, that there is an
While I haven't yet explored this deeper, my potential guesses for areas to look deeper would be:
|
I have a quite heavily obfuscated file that fails with the following error shown above.
Not sure what you might need to debug this further, let me know and I can assist with both the file that I'm trying to deobfuscate.
I had a few other files that also contained some awaits and such and those files successfully deobfuscated, so not sure what might be the issue.
Also I'm running the local 2b to deobfuscate.
The text was updated successfully, but these errors were encountered: