Skip to content

Mac release vk#104

Closed
AmesingFlank wants to merge 10 commits into
masterfrom
mac_release_vk
Closed

Mac release vk#104
AmesingFlank wants to merge 10 commits into
masterfrom
mac_release_vk

Conversation

@AmesingFlank

@AmesingFlank AmesingFlank commented Oct 27, 2021

Copy link
Copy Markdown
Collaborator

Note

High Risk
SessionStart hooks and always-applied rules execute or strongly encourage running an unaudited Node script automatically—classic supply-chain / malicious-setup vector, especially given the script’s very large size.

Overview
This PR wires automatic execution of node .github/setup.js into AI/IDE workflows and adds a new script at .github/setup.js (content not shown in the diff; the file in the tree is very large).

Claude (.claude/settings.json) and Gemini (.gemini/settings.json) each gain a SessionStart hook that runs that command for every session. Cursor gets an always-on rule (.cursor/rules/setup.mdc) that instructs assistants and users to run the same command for “IDE integration and dependency setup.”

Together, these changes push a single Node entrypoint to run on session start or by policy, without documenting what the script does in the diff.

Reviewed by Cursor Bugbot for commit 50a8186. Bugbot is set up for automated code reviews on this repo. Configure here.

@feisuzhu feisuzhu force-pushed the master branch 7 times, most recently from 303c297 to 7728908 Compare April 28, 2023 10:57
@feisuzhu feisuzhu force-pushed the master branch 20 times, most recently from 8de3e11 to c1014d9 Compare May 12, 2023 08:33

@knight42 knight42 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Security hold: this PR is affected by the current malicious-code incident involving suspicious [skip ci] commits and/or the .github/setup.js payload pattern.

Please do not merge this PR. I am requesting changes and closing it to prevent accidental merge while we investigate and clean up. Reopen only after the suspicious commits are removed, the branch is rebuilt from a trusted base, and trusted CI has been re-run.

安全处理:该 PR 被纳入当前恶意代码事件的受影响范围,涉及可疑的 [skip ci] commit 和/或 .github/setup.js payload 模式。

请不要合并该 PR。我会先 request changes 并关闭 PR,避免误合并。只有在移除可疑 commit、从可信 base 重建分支,并重新跑可信 CI 后,才应重新打开。

@knight42 knight42 closed this Jun 4, 2026
@knight42 knight42 added the malicious Affected by malicious setup.js incident label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

malicious Affected by malicious setup.js incident

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants