Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Security News
Sarah Gooding
May 1, 2024
In this episode of the Risky Business podcast, host Tom Uren chats with Socket founder and CEO Feross Aboukhadijeh. They delve into the vulnerabilities of open source software through the lens of notorious supply chain attacks like XZ-utils and Event-Stream. Feross shares how previous incidents inspired the creation of Socket, which detects and prevents such attacks by closely monitoring changes in software packages.
Ideally, developers should scrutinize every line of code they use, but that's simply not realistic. Threat actors are counting on this and some put in more effort to launch sophisticated attacks that get past static analysis. This is why Socket leverages LLMs for further analysis, to pick up on signals that are more difficult for humans to catch at scale.
With 90% of the code in most apps being open source, the volume of code that isn’t reviewed has significantly increased the risk for supply chain attacks. The episode explores how the rise of small, hyper-specific open source packages and a shift towards individual maintainers have created a wider attack surface.
The discussion touches on how open source development practices have contributed to these vulnerabilities in the ecosystem:
Check out the episode below:
Subscribe to our newsletter
Get notified when we publish new security blog posts!
Try it now
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.