Skip to content

GitHub Tightens npm Publishing After Flaw Left 1,500+ Packages Vulnerable to Hijacking

  • by

​GitHub has taken the step of expiring unvalidated npm trusted publishing configurations 48 hours after creation after researchers found that it was possible for an attacker to push new versions of a different user’s package without having to steal their credentials.

“Your configuration becomes validated and exempt from expiry after its first successful publish,” the Microsoft-owned subsidiary GitHub has taken the step of expiring unvalidated npm trusted publishing configurations 48 hours after creation after researchers found that it was possible for an attacker to push new versions of a different user’s package without having to steal their credentials.

“Your configuration becomes validated and exempt from expiry after its first successful publish,” the Microsoft-owned subsidiary  The Hacker News

Leave a Reply

Your email address will not be published. Required fields are marked *