Big news! We’re excited to announce that @npmjs will be joining @GitHub! We're thrilled to join an organization as committed to open source as we are, so that the npm registry can remain free & public forever.
You can read more about this new chapter here: buff.ly/3aYygVf
We’re live at noon EST / 9am PST with our very special guest @ronperris 😎! Feel free to ask questions on the YT live chat, in Slack (link on absoluteappsec.com) or email us at absoluteappsec@gmail.com.
youtube.com/watch?v=2bs6gQjL…
Did you ever want to know how a pentester makes their way from bug to exploit? Read about how @truesec found and exploited a bug in hot-formula-parser (CVE-2020-6836)
blog.truesec.com/2020/01/17/…
Great writeup about a remote code execution (RCE) vulnerability in the Strapi framework and the quick response by the Strapi team. bittherapy.net/post/strapi-f…
the npm security team has been hard at work building infrastructure to do behavioral analysis of npm packages at scale. vp of security, @adam_baldwin, explains what this entails ( a sneak peek at the security insights API): buff.ly/35ct9hw
We get a lot of requests from people wanting to do research around malware in the Registry. It will be really exciting to see what the community does with this data!
for years, npm has maintained the most complete corpus of malware published on the npm registry. learn more about the malware corpus by the numbers & what to look for in our security insights api: buff.ly/32nG67g
Did you miss us? Well we're back and tweeting. The npm security team has taken over the nodesecurity twitter account and will be keeping you up to date on JavaScript security related happenings.