dangerously_pull_request_target
Zach Leatherman 1010 replies 4747 likes11 repost Original on BlueskyOriginal on MastodonAlso posted to Mastodon.
10 replies
The fact that they didn't use a more obvious name makes me think they didn't really consider the security implications.
dangerously_pull_request_target_SUPER_INSECURE_WARNING_CAREFUL_WATCH_OUT
lol
@localnerve I would prefer to live a very boring life when it comes to third party dependencies 😅
But you're in GitHub Actions, an `evil_petting_zoo`
(Same actor, different costume, pinky)
@zachleat DO_NOT_USE_OR_YOU_WILL_BE_PHISHED
@mattdsteele look, if you’re ever offered phish concert tickets in an email — definitely click the link
@zachleat I read the article about Shai Hulud 2.0 this morning and am still flabbergasted by its complexity.
How are you supposed to protect your project against something like that?
@wtrmt fascinatingly enough I wrote up the steps I’ve taken 😅 https://www.zachleat.com/web/npm-security/