Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add recent reports #776
base: main
Are you sure you want to change the base?
Add recent reports #776
Changes from 1 commit
2870993
37ff366
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain more why this package is considered malicious?
It is definitely suspicious, but doesn't execute the problematic code, except if the file is excuted directly by passing it to node.js.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My original thinking was that in the package.json for this file the script eth.js with the malicious functionality is defined as the entrypoint via
main
."main": "/docs.wrm/basics/eth.js",
The archiving/exfiltration functions are the exports of
eth.js
Hence I thought upon import of the package itself, the functions are executed. But yes you are right unless it's executed like
node /docs.wrm/basics/eth.js
it won't send to the ngrok endpoint. I still think there's no good reason to have that in there, but I'm fine to remove the report if you think it doesn't pass the threshold of malicious.