
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Quickly evaluate the security and health of any open source package.
lucifer490-br
1.1.5
by luslucifer490
Live on npm
Blocked by Socket
This file defines a function that sends potentially sensitive data (via the 'key' parameter) to basseqwevewcewcewecwcw[.]xyz, a suspicious domain. The request includes a hardcoded cookie and embeds unvalidated user input in both the URL and POST body, indicating potential data exfiltration or unauthorized data transmission.
curri-slack
14.14.1000
Removed from npm
Blocked by Socket
The code is performing several malicious activities, including sending system information and file contents to external servers. This poses a significant security risk.
Live on npm for 53 minutes before removal. Socket users were protected even while the package was live.
node-validators
1.1.2
by brightstar1001
Removed from npm
Blocked by Socket
The primary concern is the network request in check_validator, which sends data to an external URL. This could pose a privacy risk if the data is sensitive and sent without user consent. The code does not appear to be obfuscated, and while it uses standard practices, the network request should be scrutinized.
Live on npm for 3 days, 11 hours and 45 minutes before removal. Socket users were protected even while the package was live.
linkinbio-web-components
1.0.0
by moresaucelesssoda
Removed from npm
Blocked by Socket
The code demonstrates clear malicious intent by exfiltrating sensitive system information, including the contents of the '/etc/passwd' file, to a remote server. This poses a significant security risk.
Live on npm for 57 minutes before removal. Socket users were protected even while the package was live.
trident-dawn-paq806-project
1.0.0
by afifcapcut112
Removed from npm
Blocked by Socket
The code itself does not exhibit directly malicious behavior, but the unusual and inconsistent naming of the imported modules and their methods, along with the lack of context for their functionality, raises red flags. The modules themselves need to be reviewed to ensure they are not performing any malicious actions. Without additional information on these modules, the risk cannot be fully assessed.
Live on npm for 56 days, 22 hours and 19 minutes before removal. Socket users were protected even while the package was live.
bv-framework-sites
8.0.5
Removed from npm
Blocked by Socket
The source code sets up a reverse shell, allowing remote command execution on the compromised system. This is a critical security threat and is indicative of malicious behavior.
Live on npm for 10 minutes before removal. Socket users were protected even while the package was live.
epic-ue-ui
6.998.5
Removed from npm
Blocked by Socket
The purpose of this code appears to be collecting specific environment variables and package information, compressing and encoding it, and sending it over HTTP to a remote domain. The intent and purpose of this behavior are unclear from the provided code fragment alone.
Live on npm for 32 minutes before removal. Socket users were protected even while the package was live.
yasap-cache
1.0.15
by meow-test
Removed from npm
Blocked by Socket
The script is designed to collect and transmit sensitive system information to a remote server, which poses a significant security risk and is indicative of malicious behavior.
Live on npm for 2 hours and 5 minutes before removal. Socket users were protected even while the package was live.
micro-username
2.1.6
by sparmar0121
Removed from npm
Blocked by Socket
The script collects information like package name, directory, home directory, hostname, username, DNS servers, and package.json data and sends it to a remote server.
Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.
elf-utils-js
1.0.2
Removed from npm
Blocked by Socket
The behavior of this script is suspicious as it runs the 'preinstall.js' file twice, once in the background and once normally. This could potentially indicate an attempt to execute malicious code or perform unauthorized actions.
Live on npm for 1 minute before removal. Socket users were protected even while the package was live.
mepjow
1.2.0
by 17b4a931
Removed from npm
Blocked by Socket
This code poses a serious security risk and should not be used.
Live on npm for 4 minutes before removal. Socket users were protected even while the package was live.
plugin-compiler-bytedance
99.11.18
by mtdev008742
Removed from npm
Blocked by Socket
The code exhibits behavior consistent with malicious activity, specifically data exfiltration to suspicious domains. It collects and sends sensitive system information without user consent, indicating a high security risk.
Live on npm for 5 days, 17 hours and 20 minutes before removal. Socket users were protected even while the package was live.
@testing.sec123/toxic-pkg-dont-use
0.0.3
Removed from npm
Blocked by Socket
The script collects the user's environment variables and sends them to an external server in base64-encoded format.
Live on npm for 4 days, 6 hours and 34 minutes before removal. Socket users were protected even while the package was live.
godaddy-sync
999.9.9
by amigomioteconsidero20
Removed from npm
Blocked by Socket
The code is designed to exfiltrate system information by sending it to an external domain via DNS queries. This is a clear indication of malicious behavior, as it involves unauthorized data transmission without user consent.
Live on npm for 2 hours and 53 minutes before removal. Socket users were protected even while the package was live.
@energysolutions/mylib
99.9.3
by zoeovpz
Live on npm
Blocked by Socket
The code is engaging in data exfiltration by collecting and sending system information to an external server without user consent.
azure-graphrbac
0.8.6
Removed from npm
Blocked by Socket
The code is confirmed to be sending system information and file contents to external servers, which is malicious behavior. The reports provided are inadequate as they do not contain any meaningful information or analysis.
Live on npm for 1 hour and 10 minutes before removal. Socket users were protected even while the package was live.
@illimity/commons
3.30.3
Removed from npm
Blocked by Socket
This package was removed from the npm registry for security reasons.
Live on npm for 30 minutes before removal. Socket users were protected even while the package was live.
bc-image-loader
8.848.3
by hsek-vdo
Removed from npm
Blocked by Socket
The code is performing malicious activities by sending environment variables to a remote server and obfuscating parts of the code. This poses a high security risk due to potential exposure of sensitive information.
Live on npm for 18 minutes before removal. Socket users were protected even while the package was live.
portm-agent
1.0.5
by 92nfdy2fd
Removed from npm
Blocked by Socket
The script is likely used for malicious purposes, collecting sensitive data and sending it to specific IPs, which can be interpreted as a data exfiltration attempt. The usage of obfuscated code and hardcoded IP addresses further supports the suspicion of malicious intent.
Live on npm for 1 hour and 6 minutes before removal. Socket users were protected even while the package was live.
link-stripper2
1.0.2
Removed from npm
Blocked by Socket
The code exhibits clear signs of malicious behavior, including executing unauthorized commands, modifying system files, and maintaining persistence. The obfuscation further suggests an attempt to hide its true purpose. It poses a significant security risk.
Live on npm for 1 hour and 25 minutes before removal. Socket users were protected even while the package was live.
metacord
1.1.9-Beta
by shinchan0911
Removed from npm
Blocked by Socket
The code contains several security risks including hardcoded credentials, lack of input validation, and potential for arbitrary code execution. It is advised to review and improve the security of the code before use.
Live on npm for 13 minutes before removal. Socket users were protected even while the package was live.
oauth-connect-popup
2.0.1
by sunnyshrm13
Removed from npm
Blocked by Socket
The code appears to collect sensitive system and user information and sends it to a remote server. This behavior is highly suspicious and may constitute a privacy violation or data theft. The use of a hardcoded remote server further raises concerns about the intent behind this code.
Live on npm for 42 minutes before removal. Socket users were protected even while the package was live.
gatsby-plugin-substrate
2.0.0
by penetolabs
Removed from npm
Blocked by Socket
The code is intentionally exfiltrating sensitive information to a suspicious remote server, likely for malicious purposes. The obfuscated hostname and the nature of the data collected indicate a strong possibility of a supply chain attack aiming to collect user data without consent. The 'pipedream' keyword is likely a coding error rather than an obfuscation attempt.
Live on npm for 1 minute before removal. Socket users were protected even while the package was live.
wixdev2022-1
1.0.6
by cthulhufhtagn1
Removed from npm
Blocked by Socket
The code snippet poses a security risk due to the use of exec to connect to an external domain. This behavior could be indicative of malicious intent, especially if the domain is not trusted.
Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.
fiji-core-pal
543.60.70
by parrotman
Removed from npm
Blocked by Socket
The code appears to be decrypting text using AES-256-CBC encryption. However, it contains obfuscated code and an 'eval' function call with potentially untrusted input. This raises concerns about the possibility of malicious behavior or code injection.
Live on npm for 31 days, 23 hours and 7 minutes before removal. Socket users were protected even while the package was live.
lucifer490-br
1.1.5
by luslucifer490
Live on npm
Blocked by Socket
This file defines a function that sends potentially sensitive data (via the 'key' parameter) to basseqwevewcewcewecwcw[.]xyz, a suspicious domain. The request includes a hardcoded cookie and embeds unvalidated user input in both the URL and POST body, indicating potential data exfiltration or unauthorized data transmission.
curri-slack
14.14.1000
Removed from npm
Blocked by Socket
The code is performing several malicious activities, including sending system information and file contents to external servers. This poses a significant security risk.
Live on npm for 53 minutes before removal. Socket users were protected even while the package was live.
node-validators
1.1.2
by brightstar1001
Removed from npm
Blocked by Socket
The primary concern is the network request in check_validator, which sends data to an external URL. This could pose a privacy risk if the data is sensitive and sent without user consent. The code does not appear to be obfuscated, and while it uses standard practices, the network request should be scrutinized.
Live on npm for 3 days, 11 hours and 45 minutes before removal. Socket users were protected even while the package was live.
linkinbio-web-components
1.0.0
by moresaucelesssoda
Removed from npm
Blocked by Socket
The code demonstrates clear malicious intent by exfiltrating sensitive system information, including the contents of the '/etc/passwd' file, to a remote server. This poses a significant security risk.
Live on npm for 57 minutes before removal. Socket users were protected even while the package was live.
trident-dawn-paq806-project
1.0.0
by afifcapcut112
Removed from npm
Blocked by Socket
The code itself does not exhibit directly malicious behavior, but the unusual and inconsistent naming of the imported modules and their methods, along with the lack of context for their functionality, raises red flags. The modules themselves need to be reviewed to ensure they are not performing any malicious actions. Without additional information on these modules, the risk cannot be fully assessed.
Live on npm for 56 days, 22 hours and 19 minutes before removal. Socket users were protected even while the package was live.
bv-framework-sites
8.0.5
Removed from npm
Blocked by Socket
The source code sets up a reverse shell, allowing remote command execution on the compromised system. This is a critical security threat and is indicative of malicious behavior.
Live on npm for 10 minutes before removal. Socket users were protected even while the package was live.
epic-ue-ui
6.998.5
Removed from npm
Blocked by Socket
The purpose of this code appears to be collecting specific environment variables and package information, compressing and encoding it, and sending it over HTTP to a remote domain. The intent and purpose of this behavior are unclear from the provided code fragment alone.
Live on npm for 32 minutes before removal. Socket users were protected even while the package was live.
yasap-cache
1.0.15
by meow-test
Removed from npm
Blocked by Socket
The script is designed to collect and transmit sensitive system information to a remote server, which poses a significant security risk and is indicative of malicious behavior.
Live on npm for 2 hours and 5 minutes before removal. Socket users were protected even while the package was live.
micro-username
2.1.6
by sparmar0121
Removed from npm
Blocked by Socket
The script collects information like package name, directory, home directory, hostname, username, DNS servers, and package.json data and sends it to a remote server.
Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.
elf-utils-js
1.0.2
Removed from npm
Blocked by Socket
The behavior of this script is suspicious as it runs the 'preinstall.js' file twice, once in the background and once normally. This could potentially indicate an attempt to execute malicious code or perform unauthorized actions.
Live on npm for 1 minute before removal. Socket users were protected even while the package was live.
mepjow
1.2.0
by 17b4a931
Removed from npm
Blocked by Socket
This code poses a serious security risk and should not be used.
Live on npm for 4 minutes before removal. Socket users were protected even while the package was live.
plugin-compiler-bytedance
99.11.18
by mtdev008742
Removed from npm
Blocked by Socket
The code exhibits behavior consistent with malicious activity, specifically data exfiltration to suspicious domains. It collects and sends sensitive system information without user consent, indicating a high security risk.
Live on npm for 5 days, 17 hours and 20 minutes before removal. Socket users were protected even while the package was live.
@testing.sec123/toxic-pkg-dont-use
0.0.3
Removed from npm
Blocked by Socket
The script collects the user's environment variables and sends them to an external server in base64-encoded format.
Live on npm for 4 days, 6 hours and 34 minutes before removal. Socket users were protected even while the package was live.
godaddy-sync
999.9.9
by amigomioteconsidero20
Removed from npm
Blocked by Socket
The code is designed to exfiltrate system information by sending it to an external domain via DNS queries. This is a clear indication of malicious behavior, as it involves unauthorized data transmission without user consent.
Live on npm for 2 hours and 53 minutes before removal. Socket users were protected even while the package was live.
@energysolutions/mylib
99.9.3
by zoeovpz
Live on npm
Blocked by Socket
The code is engaging in data exfiltration by collecting and sending system information to an external server without user consent.
azure-graphrbac
0.8.6
Removed from npm
Blocked by Socket
The code is confirmed to be sending system information and file contents to external servers, which is malicious behavior. The reports provided are inadequate as they do not contain any meaningful information or analysis.
Live on npm for 1 hour and 10 minutes before removal. Socket users were protected even while the package was live.
@illimity/commons
3.30.3
Removed from npm
Blocked by Socket
This package was removed from the npm registry for security reasons.
Live on npm for 30 minutes before removal. Socket users were protected even while the package was live.
bc-image-loader
8.848.3
by hsek-vdo
Removed from npm
Blocked by Socket
The code is performing malicious activities by sending environment variables to a remote server and obfuscating parts of the code. This poses a high security risk due to potential exposure of sensitive information.
Live on npm for 18 minutes before removal. Socket users were protected even while the package was live.
portm-agent
1.0.5
by 92nfdy2fd
Removed from npm
Blocked by Socket
The script is likely used for malicious purposes, collecting sensitive data and sending it to specific IPs, which can be interpreted as a data exfiltration attempt. The usage of obfuscated code and hardcoded IP addresses further supports the suspicion of malicious intent.
Live on npm for 1 hour and 6 minutes before removal. Socket users were protected even while the package was live.
link-stripper2
1.0.2
Removed from npm
Blocked by Socket
The code exhibits clear signs of malicious behavior, including executing unauthorized commands, modifying system files, and maintaining persistence. The obfuscation further suggests an attempt to hide its true purpose. It poses a significant security risk.
Live on npm for 1 hour and 25 minutes before removal. Socket users were protected even while the package was live.
metacord
1.1.9-Beta
by shinchan0911
Removed from npm
Blocked by Socket
The code contains several security risks including hardcoded credentials, lack of input validation, and potential for arbitrary code execution. It is advised to review and improve the security of the code before use.
Live on npm for 13 minutes before removal. Socket users were protected even while the package was live.
oauth-connect-popup
2.0.1
by sunnyshrm13
Removed from npm
Blocked by Socket
The code appears to collect sensitive system and user information and sends it to a remote server. This behavior is highly suspicious and may constitute a privacy violation or data theft. The use of a hardcoded remote server further raises concerns about the intent behind this code.
Live on npm for 42 minutes before removal. Socket users were protected even while the package was live.
gatsby-plugin-substrate
2.0.0
by penetolabs
Removed from npm
Blocked by Socket
The code is intentionally exfiltrating sensitive information to a suspicious remote server, likely for malicious purposes. The obfuscated hostname and the nature of the data collected indicate a strong possibility of a supply chain attack aiming to collect user data without consent. The 'pipedream' keyword is likely a coding error rather than an obfuscation attempt.
Live on npm for 1 minute before removal. Socket users were protected even while the package was live.
wixdev2022-1
1.0.6
by cthulhufhtagn1
Removed from npm
Blocked by Socket
The code snippet poses a security risk due to the use of exec to connect to an external domain. This behavior could be indicative of malicious intent, especially if the domain is not trusted.
Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.
fiji-core-pal
543.60.70
by parrotman
Removed from npm
Blocked by Socket
The code appears to be decrypting text using AES-256-CBC encryption. However, it contains obfuscated code and an 'eval' function call with potentially untrusted input. This raises concerns about the possibility of malicious behavior or code injection.
Live on npm for 31 days, 23 hours and 7 minutes before removal. Socket users were protected even while the package was live.
Socket detects traditional vulnerabilities (CVEs) but goes beyond that to scan the actual code of dependencies for malicious behavior. It proactively detects and blocks 70+ signals of supply chain risk in open source code, for comprehensive protection.
Known malware
Possible typosquat attack
NPM Shrinkwrap
Git dependency
HTTP dependency
Suspicious Stars on GitHub
Protestware or potentially unwanted behavior
Unstable ownership
AI-detected potential malware
Obfuscated code
20 more alerts →
Bad dependency semver
Wildcard dependency
Unpopular package
Minified code
Socket optimized override available
Deprecated
Unmaintained
Critical CVE
High CVE
Medium CVE
Low CVE
Explicitly Unlicensed Item
License Policy Violation
Misc. License Issues
Non-permissive License
Ambiguous License Classifier
Copyleft License
Unidentified License
No License Found
License exception
Socket detects and blocks malicious dependencies, often within just minutes of them being published to public registries, making it the most effective tool for blocking zero-day supply chain attacks.
Socket is built by a team of prolific open source maintainers whose software is downloaded over 1 billion times per month. We understand how to build tools that developers love. But don’t take our word for it.
Nat Friedman
CEO at GitHub
Congrats to @feross and the hard-working team behind @SocketSecurity on today's launch!
Suz Hinton
Senior Software Engineer at Stripe
heck yes this is awesome!!! Congrats team 🎉👏
Matteo Collina
Node.js maintainer, Fastify lead maintainer
So awesome to see @SocketSecurity launch with a fresh approach! Excited to have supported the team from the early days.
DC Posch
Director of Technology at AppFolio, CTO at Dynasty
This is going to be super important, especially for crypto projects where a compromised dependency results in stolen user assets.
Luis Naranjo
Software Engineer at Microsoft
If software supply chain attacks through npm don't scare the shit out of you, you're not paying close enough attention.
@SocketSecurity sounds like an awesome product. I'll be using socket.dev instead of npmjs.org to browse npm packages going forward
Elena Nadolinski
Founder and CEO at Iron Fish
Huge congrats to @SocketSecurity! 🙌
Literally the only product that proactively detects signs of JS compromised packages.
Joe Previte
Engineering Team Lead at Coder
Congrats to @feross and the @SocketSecurity team on their seed funding! 🚀 It's been a big help for us at @CoderHQ and we appreciate what y'all are doing!
Josh Goldberg
Staff Developer at Codecademy
This is such a great idea & looks fantastic, congrats & good luck @feross + team!
The best security teams in the world use Socket to get visibility into supply chain risk, and to build a security feedback loop into the development process.
Yan Zhu
Head of Security at Brave, DEFCON, EFF, W3C
glad to hear some of the smartest people i know are working on (npm, etc.) supply chain security finally :). @SocketSecurity
Andrew Peterson
CEO and Co-Founder at Signal Sciences (acq. Fastly)
How do you track the validity of open source software libraries as they get updated? You're prob not. Check out @SocketSecurity and the updated tooling they launched.
Supply chain is a cluster in security as we all know and the tools from Socket are "duh" type tools to be implementing.
Zbyszek Tenerowicz
Senior Security Engineer at ConsenSys
socket.dev is getting more appealing by the hour
Devdatta Akhawe
Head of Security at Figma
The @SocketSecurity team is on fire! Amazing progress and I am exciting to see where they go next.
Ryan Noon
Founder & CEO at Material Security
The NPM ecosystem is a horrible horrible place and I'm glad you're doing something about it.
Sebastian Bensusan
Engineer Manager at Stripe
I find it surprising that we don't have _more_ supply chain attacks in software:
Imagine your airplane (the code running) was assembled (deployed) daily, with parts (dependencies) from internet strangers. How long until you get a bad part?
Excited for Socket to prevent this
Adam Baldwin
VP of Security at npm, Red Team at Auth0/Okta
Congrats to everyone at @SocketSecurity ❤️🤘🏻
Nico Waisman
CISO at Lyft
This is an area that I have personally been very focused on. As Nat Friedman said in the 2019 GitHub Universe keynote, Open Source won, and every time you add a new open source project you rely on someone else's code and you rely on the people that build it.
This is both exciting and problematic. You are bringing real risk into your organization, and I'm excited to see progress in the industry from OpenSSF scorecards and package analyzers to the company that Feross Aboukhadijeh is building!
Depend on Socket to prevent malicious open source dependencies from infiltrating your app.
Install the Socket GitHub App in just 2 clicks and get protected today.
Block 70+ issues in open source code, including malware, typo-squatting, hidden code, misleading packages, permission creep, and more.
Reduce work by surfacing actionable security information directly in GitHub. Empower developers to make better decisions.
Attackers have taken notice of the opportunity to attack organizations through open source dependencies. Supply chain attacks rose a whopping 700% in the past year, with over 15,000 recorded attacks.
Dec 14, 2023
Hijacked cryptocurrency library adds malware
Widely-used library in cryptocurrency frontend was compromised to include wallet-draining code, following the hijacking of NPM account credentials via phishing.
Jan 06, 2022
Maintainer intentionally adds malware
Rogue maintainer sabotages his own open source package with 100M downloads/month, notably breaking Amazon's AWS SDK.
Nov 15, 2021
npm discovers a platform vulnerability allowing unauthorized publishing of any package
Attackers could publish new versions of any npm package without authorization for multiple years.
Oct 22, 2021
Hijacked package adds cryptominers and password-stealing malware
Multiple packages with 30M downloads/month are hijacked and publish malicious versions directly into the software supply chain.
Nov 26, 2018
Package hijacked adding organization specific backdoors
Obfuscated malware added to a dependency which targeted a single company, went undetected for over a week, and made it into their production build.
Get our latest security research, open source insights, and product updates.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.