👀 in your Dependency Insights for evidence of using the Action
👀 in your Dependency Insights for evidence of using the Action
Guess which Action I used as an example in the README. Yep, you guessed it... 🔮
Guess which Action I used as an example in the README. Yep, you guessed it... 🔮
🚨 Security response. Check your logs, rotate and revoke credentials, etc.
📌 Make sure you're using pinned commits to 3rd party Actions. Pinning to a tag name is not enough 🙅♂️ to avoid this.
⚠️ Read the StepSecurity advisory (they detected it): www.stepsecurity.io/blog/harden-...
🚨 Security response. Check your logs, rotate and revoke credentials, etc.
📌 Make sure you're using pinned commits to 3rd party Actions. Pinning to a tag name is not enough 🙅♂️ to avoid this.
⚠️ Read the StepSecurity advisory (they detected it): www.stepsecurity.io/blog/harden-...
The repo is back under the maintainer’s control.
The repo is back under the maintainer’s control.
🚨 security response. Logs, rotate/revoke secrets, etc.
📌 Pin your commits
🔎 Search for uses with GitHub Code Search, e.g.
github.com/search?q=%2F...
👀 Look in Dependency Insights for uses of these reviewdog Actions
🚨 security response. Logs, rotate/revoke secrets, etc.
📌 Pin your commits
🔎 Search for uses with GitHub Code Search, e.g.
github.com/search?q=%2F...
👀 Look in Dependency Insights for uses of these reviewdog Actions
Malicious commit: github.com/reviewdog/ac...
Hash: f0d342d24037bb11d26b9bd8496e0808ba32e9ec
Malicious commit: github.com/reviewdog/ac...
Hash: f0d342d24037bb11d26b9bd8496e0808ba32e9ec