Socket

2.9K posts

Socket banner
Socket

Socket

@SocketSecurity

Socket is the #1 software supply chain security platform. Next-gen SCA + SBOM + 0-day prevention. LOVED BY DEVELOPERS. 👀 @npm_malware

https://socket.dev/careers Katılım Kasım 2021
4.6K Takip Edilen11.1K Takipçiler
Sabitlenmiş Tweet
Socket
Socket@SocketSecurity·
🚀 We’re thrilled to announce Socket’s $40M Series B led by @AbstractVC with participation from @eladgil and @a16z!
Socket tweet media
English
16
17
98
51.8K
Socket
Socket@SocketSecurity·
Following a security audit, PyPI fixed two high-severity access control issues affecting organization owner invites and project transfer permissions. The audit also surfaced issues in trusted publishing and wheel metadata validation. socket.dev/blog/pypi-fixe… #Python
English
1
6
27
2.7K
Socket retweetledi
Feross
Feross@feross·
PSA: Socket is free for open source maintainers.
Feross@feross

Socket is free for open source maintainers. We're launching the @SocketSecurity for Open Source program -- any open source maintainer can get a free Team plan to protect their project from supply chain attacks. Open source is critical infrastructure. Millions of companies depend on packages maintained by small teams and volunteers. These maintainers are high-value targets but rarely have access to enterprise security tooling. That's wrong. We want to fix it. What you get: ✅ Full dependency scanning across your project ✅ Real-time alerts for malicious packages in your dependency tree ✅ Check every PR to make sure no malicious dependencies are added -- including PRs from outside contributors If you maintain an open source project, send an email to support[at]socket[dot]dev and we'll get you set up!

English
1
8
68
12.4K
Socket retweetledi
Sarah Gooding
Sarah Gooding@sarahgooding·
🔥 "Within minutes, our community found, reported, and escalated this issue helped stop the damage from spreading. A closed-source vendor can't say the same. The speed witnessed today was only possible because thousands of experts in this community have eyes on our software 24/7/365."
Lightning AI ⚡️@LightningAI

Yesterday the open source community spotted a supply chain attack on PyTorch Lightning and contained it in 42 minutes. Community members flagged unusual behavior, reported it, and stopped it before it spread. Compromised versions (2.6.2, 2.6.3) were live between 12:45–13:27 UTC. This affected distribution only. The GitHub repo was never touched. Thanks to the community for the quick reports, to @pypi for quarantining the packages, and to @SocketSecurity for surfacing detailed analysis. Read the full report → go.lightning.ai/4n5vGTO

English
0
3
6
2.9K
Socket retweetledi
tuckner
tuckner@tuckner·
I got a chance to do an interview with Bank Info Security that I think really captures the opportunity ahead for @SocketSecurity - More people developing with few knowledgeable of the footguns - Supply chain is fully developer to consumer now - Teams are looking for a way to handle all these new ecosystems and capabilities bankinfosecurity.com/socket-buys-se…
English
0
2
11
2K
Socket retweetledi
Ahmad Nassri
Ahmad Nassri@AhmadNassri·
Today's "Mini Shai-Hulud" supply chain attack is a wild evolution in open-source threats! 1. Cascading, cross-ecosystem propagation (@pypi ➡️ @npmjs ➡️ @packagist) 2. Using a JS runtime (Bun) to infect Python and PHP 3. Impersonates Claude in git commits to hide in plain sight 4. Exploiting Packagist / GitHub tag mutability 5. Exploits Composer plugins functionality, mimicking npm's "postinstall" (a first!) 6. Audacious trolling on GitHub issues of compromised packages socket.dev/blog/mini-shai…
English
0
6
9
2K
Socket retweetledi
jasonsaayman
jasonsaayman@jasonsaayman·
Wow! Across three ecosystems. It seems the largest risk is post / pre / during install hooks or execution. Point of failure is still in the install process.
Socket@SocketSecurity

🚨 BREAKING: Mini Shai-Hulud has spread to Packagist. We detected a malicious intercom/intercom-php@5.0.2 package artifact tied to this campaign. The compromised #PHP package used Composer plugin execution to run during install/update, download Bun, and launch an obfuscated router_runtime.js credential-stealing payload. It targeted GitHub, npm, SSH, cloud, Kubernetes, Vault, Docker, .env files, and more. We reported it to @packagist, which removed the malicious version.

English
0
3
8
2.7K
Socket retweetledi
Lightning AI ⚡️
Lightning AI ⚡️@LightningAI·
Yesterday the open source community spotted a supply chain attack on PyTorch Lightning and contained it in 42 minutes. Community members flagged unusual behavior, reported it, and stopped it before it spread. Compromised versions (2.6.2, 2.6.3) were live between 12:45–13:27 UTC. This affected distribution only. The GitHub repo was never touched. Thanks to the community for the quick reports, to @pypi for quarantining the packages, and to @SocketSecurity for surfacing detailed analysis. Read the full report → go.lightning.ai/4n5vGTO
Lightning AI ⚡️ tweet media
English
2
11
25
7.2K
Socket retweetledi
The Hacker News
The Hacker News@TheHackersNews·
😬 Poisoned Ruby gems + Go modules used in a supply chain attack. • Steal AWS creds, SSH keys, configs • Tamper GitHub Actions via fake binaries • Add SSH access for persistence Read → thehackernews.com/2026/05/poison…
English
2
29
64
11.8K
Socket retweetledi
William Falcon ⚡️
William Falcon ⚡️@williamfalcon·
Yesterday we saw a supply-chain attack on PyTorch Lightning (on Pypi, not our core repo). It's wild how it happened but it was caught and quarantined within 42 minutes thanks to the open source community. It's one reason why open source actually helps increase the security posture of projects. Thank you to @pypi and @SocketSecurity ⚡️ Summary: On April 30th, 2026, an attacker captured PyPI credentials and used them to push compromised versions of PyTorch Lightning (PTL). These versions were live for 42 minutes before PTL community members alerted us and PyPI quarantined the package. The PyTorch Lightning GitHub source code repository was never compromised. This affected those who installed PTL via PyPI between 12:45:20 and 13:27:30 UTC on April 30th, 2026. lightning.ai/blog/pytorch-l…
English
1
14
50
3.8K
Socket retweetledi
acxtrilla
acxtrilla@acxtrila·
"I added malware to a package named after a popular framework but forgot to remove it, oops!"
GIF
English
1
5
31
2.7K
Socket
Socket@SocketSecurity·
New Research: Malicious Ruby gems and Go modules impersonated developer tools to steal secrets and poison CI. Socket researchers found credential theft, GitHub Actions tampering, fake Go wrappers, proxy manipulation, and SSH persistence. socket.dev/blog/malicious… #golang
English
4
7
33
3.5K
Socket retweetledi
Feross
Feross@feross·
Update (April 30, 19:46:2): Intercom has confirmed to Socket that the root cause of the compromise was a local install of pyannote-audio, which introduced the compromised lightning package as a transitive dependency. That finding connects the attack chain across three ecosystems: the PyPI lightning compromise led to the npm intercom-client compromise, which was then followed by the malicious Packagist artifact for intercom/intercom-php. Intercom confirmed the pyannote-audio package was installed directly by a user locally and was not related to other repositories.
Feross@feross

🚨 Two major supply chain attacks today, hitting both PyPI and npm simultaneously. Socket detected and confirmed malicious code in lightning versions 2.6.2 and 2.6.3 on PyPI, and intercom-client version 7.0.4 on npm. Both attacks use nearly identical tooling. Both are live right now. lightning is one of the most popular deep learning frameworks in the Python ecosystem, with millions of downloads per month. intercom-client is Intercom's official Node.js SDK, with roughly 360K weekly downloads. These are not typosquats. These are the real packages. The payloads are almost identical across both attacks: • Both inject an ~11MB obfuscated JavaScript file (router_runtime.js) and a setup script that downloads and executes the Bun runtime from GitHub • Both harvest GitHub tokens, npm tokens, AWS/Azure/GCP credentials, Kubernetes secrets, Vault tokens, and CI/CD environment variables • Both exfiltrate stolen credentials through the GitHub API • Both execute automatically, lightning on import, intercom-client on install The lightning attack goes further. It uses stolen GitHub tokens to commit poisoned files to every branch of every repository the token can write to, impersonating Anthropic's Claude Code as the committer (claude@users.noreply.github.com). It also infects local npm tarballs by injecting a postinstall hook and bumping the patch version, so the next publish silently ships malware to downstream users. In both cases, the attackers appear to have compromised maintainer accounts and used them to suppress disclosure. On the Lightning-AI GitHub, the pl-ghost account closed Socket's disclosure issue within one minute and posted a meme. On the Intercom GitHub, the nhur account closed, redacted, and retitled security reports to "N/A." Both accounts show bursts of suspicious branch-creation activity consistent with the Shai-Hulud worm's credential-probing pattern, including misspelled Dependabot impersonation branches. The attackers posted an onion link in the Lightning-AI issue thread claiming affiliation with "Team PCP" and referencing LAPSUS$. Socket has not verified these claims. The intercom-client attack also shows direct Shai-Hulud hallmarks, including repos created with descriptions reading "A Mini Shai-Hulud has Appeared." Socket's AI scanner flagged the malicious lightning versions 18 minutes after publication. If you use either package: • Remove lightning 2.6.2/2.6.3 and intercom-client 7.0.4 immediately • Downgrade to lightning 2.6.1 / intercom-client 7.0.3 • Rotate all credentials in affected environments • Audit repos for unauthorized commits from claude@users.noreply.github.com and unexpected files in .claude/ or .vscode/ • More advice in our full research posts... This is the same attacker campaign operating across two language ecosystems simultaneously. The playbook is credential theft, repo poisoning, and worm-style propagation. The scope is still being determined. Developing story...

English
2
15
80
28.3K
Socket
Socket@SocketSecurity·
Update: Socket confirmed the Intercom compromise began with a local install of pyannote-audio, which pulled in compromised PyPI lightning as a transitive dependency. 🤯 That single install kicked off a chain of compromises: PyPI lightning → npm intercom-client → Packagist intercom/intercom-php One malicious dependency worming its way across three ecosystems.
Socket@SocketSecurity

🚨 BREAKING: Mini Shai-Hulud has spread to Packagist. We detected a malicious intercom/intercom-php@5.0.2 package artifact tied to this campaign. The compromised #PHP package used Composer plugin execution to run during install/update, download Bun, and launch an obfuscated router_runtime.js credential-stealing payload. It targeted GitHub, npm, SSH, cloud, Kubernetes, Vault, Docker, .env files, and more. We reported it to @packagist, which removed the malicious version.

English
3
25
98
14.7K
Socket retweetledi
SaltyAom
SaltyAom@saltyAom·
Boohoo not cool man > Register many names similar to Tanstack > Create a README to make it look like one > All created just a year ago > Ransom $10k from Tanner > Publish malware to steal .env This is not an accident, this is an intentional malicious behavior Shame on you @SH20RAJ for making the job of Open Source maintainers harder than it already is I sincerely hope your employer know what you did and that you shouldn’t be trusted or get blacklisted on your future employment
SaltyAom tweet media
Socket@SocketSecurity

🚨 A brand-squatting npm package impersonating TanStack shipped malicious versions that exfiltrate environment variables from developers’ machines during install. We spoke to @tannerlinsley, creator of @tan_stack, who confirmed that the maintainer of the unscoped tanstack package is not associated with TanStack or the official @tanstack/* projects in any way. The package is unrelated to the project's official CLI, and represents an ongoing brandjacking issue. He also said TanStack has filed legal documents related to a pending trademark infringement claim against the maintainer, that the maintainer previously demanded $10,000 from him, and that TanStack has repeatedly tried, unsuccessfully, to get @npmjs to address the situation.

English
32
70
967
89.2K
Socket retweetledi
Nils Adermann
Nils Adermann@naderman·
Thanks to @SocketSecurity for quickly alerting us, so we could take down malicious intercom packages. First time we saw malware mimicking post install scripts not available in PHP with a plugin. Fortunately requires user input to enable a plugin, so no automatic execution in CI.
Socket@SocketSecurity

🚨 BREAKING: Mini Shai-Hulud has spread to Packagist. We detected a malicious intercom/intercom-php@5.0.2 package artifact tied to this campaign. The compromised #PHP package used Composer plugin execution to run during install/update, download Bun, and launch an obfuscated router_runtime.js credential-stealing payload. It targeted GitHub, npm, SSH, cloud, Kubernetes, Vault, Docker, .env files, and more. We reported it to @packagist, which removed the malicious version.

English
1
7
33
6.6K
Socket retweetledi
Dark Web Informer
Dark Web Informer@DarkWebInformer·
‼️ Mini Shai-Hulud Malware Reaches Packagist Through Compromised Intercom PHP Package, Mirroring Earlier npm Attack 👇
Socket@SocketSecurity

🚨 BREAKING: Mini Shai-Hulud has spread to Packagist. We detected a malicious intercom/intercom-php@5.0.2 package artifact tied to this campaign. The compromised #PHP package used Composer plugin execution to run during install/update, download Bun, and launch an obfuscated router_runtime.js credential-stealing payload. It targeted GitHub, npm, SSH, cloud, Kubernetes, Vault, Docker, .env files, and more. We reported it to @packagist, which removed the malicious version.

English
0
4
15
7.1K
Socket
Socket@SocketSecurity·
This is a developing story and the third supply chain attack we've reported on today. We're monitoring for more activity across the Mini Shai-Hulud campaign. Read more: socket.dev/blog/mini-shai…
English
1
1
11
1.9K
Socket
Socket@SocketSecurity·
🚨 BREAKING: Mini Shai-Hulud has spread to Packagist. We detected a malicious intercom/intercom-php@5.0.2 package artifact tied to this campaign. The compromised #PHP package used Composer plugin execution to run during install/update, download Bun, and launch an obfuscated router_runtime.js credential-stealing payload. It targeted GitHub, npm, SSH, cloud, Kubernetes, Vault, Docker, .env files, and more. We reported it to @packagist, which removed the malicious version.
Socket tweet media
English
3
40
121
45.8K
Socket retweetledi
Feross
Feross@feross·
🚨 Two major supply chain attacks today, hitting both PyPI and npm simultaneously. Socket detected and confirmed malicious code in lightning versions 2.6.2 and 2.6.3 on PyPI, and intercom-client version 7.0.4 on npm. Both attacks use nearly identical tooling. Both are live right now. lightning is one of the most popular deep learning frameworks in the Python ecosystem, with millions of downloads per month. intercom-client is Intercom's official Node.js SDK, with roughly 360K weekly downloads. These are not typosquats. These are the real packages. The payloads are almost identical across both attacks: • Both inject an ~11MB obfuscated JavaScript file (router_runtime.js) and a setup script that downloads and executes the Bun runtime from GitHub • Both harvest GitHub tokens, npm tokens, AWS/Azure/GCP credentials, Kubernetes secrets, Vault tokens, and CI/CD environment variables • Both exfiltrate stolen credentials through the GitHub API • Both execute automatically, lightning on import, intercom-client on install The lightning attack goes further. It uses stolen GitHub tokens to commit poisoned files to every branch of every repository the token can write to, impersonating Anthropic's Claude Code as the committer (claude@users.noreply.github.com). It also infects local npm tarballs by injecting a postinstall hook and bumping the patch version, so the next publish silently ships malware to downstream users. In both cases, the attackers appear to have compromised maintainer accounts and used them to suppress disclosure. On the Lightning-AI GitHub, the pl-ghost account closed Socket's disclosure issue within one minute and posted a meme. On the Intercom GitHub, the nhur account closed, redacted, and retitled security reports to "N/A." Both accounts show bursts of suspicious branch-creation activity consistent with the Shai-Hulud worm's credential-probing pattern, including misspelled Dependabot impersonation branches. The attackers posted an onion link in the Lightning-AI issue thread claiming affiliation with "Team PCP" and referencing LAPSUS$. Socket has not verified these claims. The intercom-client attack also shows direct Shai-Hulud hallmarks, including repos created with descriptions reading "A Mini Shai-Hulud has Appeared." Socket's AI scanner flagged the malicious lightning versions 18 minutes after publication. If you use either package: • Remove lightning 2.6.2/2.6.3 and intercom-client 7.0.4 immediately • Downgrade to lightning 2.6.1 / intercom-client 7.0.3 • Rotate all credentials in affected environments • Audit repos for unauthorized commits from claude@users.noreply.github.com and unexpected files in .claude/ or .vscode/ • More advice in our full research posts... This is the same attacker campaign operating across two language ecosystems simultaneously. The playbook is credential theft, repo poisoning, and worm-style propagation. The scope is still being determined. Developing story...
Feross tweet media
English
12
46
456
692.5K