Repository navigation
security: extend static checks for Drips Wave malware indicators - #327
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Extend the existing malware guard to cover the Drips/Wave indicators: automatic VS Code tasks, fake font payloads, setup/API package loaders, hidden config code, known marker variants, and propagation artifacts.
The check reads tracked Git blobs without installing dependencies, importing project code, or invoking package scripts. It uses a read-only token, disables persisted checkout credentials, pins checkout to a commit, and runs on every PR and push.
Validation: detector regression tests pass, and the detector was run against the scanned default branch and fetched contributor PR heads. This is a targeted indicator check, not proof that every dependency or developer machine is clean.