I joined @SocketSecurity as Sales Engineer, Commercial! Excited to deep dive into software supply chain security and discussions with customers 🎉
SocketにSales Engineerとしてジョインしました!これからまた技術を通してお客様とお話できるのが楽しみです😊
🚨 Mini Shai-Hulud/Miasma has now spread to PyPI.
Socket found 37 malicious artifacts across 19 PyPI packages.
The packages abuse #Python .pth startup behavior to launch a Bun-powered credential stealer targeting developer, cloud, and CI/CD secrets.
https://t.co/tYhmMqvjyw
RubyGems 4.0.13 adds a cooldown feature to Bundler for newly published gems.
The opt-in setting lets projects delay dependency resolution for new gem versions, reducing exposure during the short window when malicious releases often spread fastest.
https://t.co/c537BrueJj
📦 @pnpmjs 11.5 adds support for recognizing npm staged publishes after staged approval metadata triggered a false downgrade signal.
As npm adds more release paths, registry metadata needs to make it clear how each package version was published.
https://t.co/hNerib86mu
💸 The Department of Commerce has released a sharply critical audit report on NIST’s management of the National Vulnerability Database.
Federal auditors found NIST:
• Had no strategic plan to clear NVD backlog
• Set an unrealistic backlog deadline
• Delayed use of CISA enrichment data
• Failed to prioritize KEVs quickly
• Relied on inefficient enrichment processes
• Eroded trust in the NVD through poor communication
The report also found that NIST and CISA ran overlapping enrichment programs without coordination, sometimes using the same contractor to perform the same work. Auditors identified at least 21,000 duplicated enrichment activities and ~$200K in wasted funds.
https://t.co/TuExuk5iWE
🚨 Active supply chain attack: A mini Shai-Hulud campaign hit npm packages under the @redhat-cloud-services namespace.
The compromised packages execute install-time malware to harvest developer and CI/CD secrets, with encrypted exfiltration and GitHub-based fallback mechanisms.
Rust is moving toward a formal LLM contribution policy after months of heated internal debate, driven by a wave of low-effort "slop PRs" straining maintainers. The proposal bans LLM authorship but allows private use.
https://t.co/ec83y49xCs
Famous Chollima, the North Korean threat group known for fake job interview lures, appears to have used a PHP/Packagist package path in a targeted developer lure.
We found the loader in a compromised Laravel package, on a branch that could be installed through Composer. It was appended after a normal Tailwind config and used TRON, Aptos, and BNB Smart Chain RPC infrastructure to retrieve and run remote JavaScript.
Developers should be careful with “interview task” or “take-home project” requests that ask them to clone a repo, check out a specific branch, or install an exact dev dependency.
New research: A malicious NuGet package impersonating Sicoob’s official SDK exfiltrated client IDs, PFX passwords, and banking certificates through Sentry telemetry.
A fake SDK for stealing API secrets:
https://t.co/zn7Y1TYoWT
Open source maintainers were already overloaded. AI-driven vulnerability discovery is about to send a lot more findings their way.
@feross on @tbpn 👇 https://t.co/bhzqK84LmM #oss
OSV has withdrawn 157 malware reports after automated detections incorrectly flagged npm and PyPI packages as malicious, pushing bad records for trusted projects into OSV-consuming security tools and CI/CD systems.
https://t.co/wKShstdUaD
🚨 ALERT: TrapDoor malware is targeting crypto and AI developers via a supply chain attack, deploying 34 malicious packages to steal wallets, SSH keys, and API keys.
The malware also injects hidden instructions to hijack AI coding assistants including Claude and Cursor.
Can someone please explain to me why we are still waiting until AFTER a package is published and distributed to take action?
Why doesn’t npm scan packages with Socket or similar before allowing them to be distributed?