Secure your dependencies. Ship with confidence.

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as protestware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The code is exfiltrating environment variables to an external server, which is a serious security concern. This action is indicative of data theft and should be considered malicious.

Live on npm for 5 hours and 57 minutes before removal. Socket users were protected even while the package was live.

The code poses a potential security risk due to the execution of `sendSystemData`, which may send system data over the network. The dynamic modification of package files is also suspicious. Further investigation into the `collector` module is necessary to determine the exact nature of `sendSystemData`.

Live on npm for 9 hours and 16 minutes before removal. Socket users were protected even while the package was live.

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.

The code poses a significant security risk as it writes and executes an unknown executable with elevated privileges. This behavior is consistent with malicious activities and could lead to unauthorized actions on the system.

Live on npm for 2 hours and 32 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it collects and transmits sensitive user data to an external server without consent, posing a significant risk to user privacy and security.

Live on npm for 19 days, 19 hours and 27 minutes before removal. Socket users were protected even while the package was live.

This code collects extensive system information and sends it to a hardcoded Slack webhook URL. This behavior is suspicious as it constitutes data exfiltration. The presence of a hardcoded URL and the collection of sensitive information such as user details, filesystem info, and network interfaces indicate potentially malicious intent.

This file decodes and immediately executes an obfuscated payload that imports fs, os, child_process, https, and path. It performs an HTTPS GET to https://mainnet[.]unstoppableapi[.]xyz/v2/id=2199046105100425&secret=iREMmhXBnAwk, writes the response into a temporary script (replacing .ps1 with .vbs on Windows), and then spawns a detached shell process with execution-policy bypass (PowerShell.exe) or nohup (wscript.exe/osascript/bash) to run the downloaded code without user consent. All operations silence output (ignore stdio) and suppress errors, indicating a backdoor or downloader behavior that poses a critical supply-chain security risk.

The code contains highly suspicious behavior likely indicative of a backdoor, including fetching and executing shell commands from a hard-coded IP address upon instantiation of the Client class. This behavior poses a severe security risk.

Live on npm for 5 hours and 33 minutes before removal. Socket users were protected even while the package was live.

This package is malicious in nature, embedding explicit adult content and suspicious external links within what should be source code. It does not contain legitimate software logic and is likely a supply chain compromise used to distribute spam or malware. The provided reports are invalid and do not analyze the content. The package should be rejected and blacklisted due to high malware and security risk scores.

This is clearly malicious code implementing a supply chain attack. It loads and executes arbitrary JavaScript from a typosquatting domain, particularly when initial validation fails. The code uses obfuscation techniques and represents a serious security threat.

Live on npm for 4 hours and 41 minutes before removal. Socket users were protected even while the package was live.

The package 'node-webcam@0.8.2' includes a post-installation script that downloads an executable file ('CommandCam.exe') from an external source without validation or integrity checks. Specifically, when installed on Windows systems, the script retrieves 'CommandCam.exe' from 'https://github[.]com/chuckfairy/node-webcam/releases/download/v0.6/CommandCam.exe' and saves it to 'src/bindings/CommandCam/CommandCam.exe' without obtaining user consent. CommandCam.exe (SHA256: 012d3ff83b1e65182807512fc9d04bcfdb40736fcdc2f7aba57531cbf031769e) is flagged as malicious by 22 out of 71 security vendors on VirusTotal. Downloading and executing binaries from external sources without validation introduces a security vulnerability, as the external source could be compromised to deliver malicious code, leading to potential arbitrary code execution on the user's system.

This code is highly suspicious and should not be used without further investigation. The code is heavily obfuscated and could potentially contain malicious code. The purpose of the code is unclear and further investigation is necessary to determine its exact behavior.

Live on npm for 12 minutes before removal. Socket users were protected even while the package was live.

The code exhibits malicious behavior by collecting and transmitting sensitive system information to a suspicious domain without user consent. This poses a significant security risk.

Live on npm for 4 days, 2 hours and 37 minutes before removal. Socket users were protected even while the package was live.

The code collects sensitive system information without user consent and sends it to an external server via a Discord webhook. The code gathers data such as the user's internal IP address, external IP address (obtained via an HTTP request to 'https[:]//ipinfo[.]io/json'), hostname, username, home directory, DNS server information, and package details from 'package.json'. This information is then formatted into a JSON object and transmitted to a hardcoded Discord webhook URL ('https[:]//discord[.]com/api/webhooks/...'). This behavior constitutes unauthorized data exfiltration and poses significant privacy and security risks.

Live on npm for 15 days, 2 hours and 35 minutes before removal. Socket users were protected even while the package was live.

This code exhibits behavior consistent with data exfiltration, employing both direct HTTP(S) transmission and covert DNS queries as a fallback mechanism. The obfuscation, target domain, and sophisticated fallback mechanism significantly raise suspicions of malicious intent.

Live on npm for 4 minutes before removal. Socket users were protected even while the package was live.

The script poses a high security risk as malware due to its ability to alter disk partitions without user interaction, leading to data loss or system damage.

The code exhibits behavior consistent with potential malware, as it decodes and executes an unknown binary with elevated privileges. This poses a significant security risk.

Live on npm for 13 days, 21 hours and 10 minutes before removal. Socket users were protected even while the package was live.

The code is indeed malicious, performing potentially harmful activities such as gathering system information and sending it to an external server via DNS requests. It poses a serious security risk due to its potential for data exfiltration.

Live on npm for 7 minutes before removal. Socket users were protected even while the package was live.

Possible typosquat of azure - Explanation: The package 'azure-graphrbac' is labeled as a 'security holding package', which often indicates a placeholder to prevent typosquatting. The name 'azure-graphrbac' closely resembles legitimate Azure package naming conventions, which could confuse users. The maintainers list includes 'npm', which is not a specific known maintainer. Therefore, it is likely a typosquat.

Live on npm for 2 hours and 28 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it covertly collects and transmits sensitive system and user environment data to an external endpoint without consent. This constitutes data exfiltration and poses a high security risk. The code is straightforward and not obfuscated, but the intent and effect are clearly malicious. It should be flagged and avoided.

Live on npm for 2 hours and 37 minutes before removal. Socket users were protected even while the package was live.

The code exhibits behavior characteristic of malware, including the collection of sensitive data, use of obfuscation, and execution of potentially arbitrary code using eval. The intentional obfuscation and disabling of NODE_NO_EVAL are indicative of an attempt to hide malicious behavior and enable unsafe operations.

Live on npm for 1 hour and 33 minutes before removal. Socket users were protected even while the package was live.

This source code is malicious. It performs stealthy data exfiltration of sensitive system and environment information to a suspicious hardcoded IP address. The evasion techniques and randomized network behavior indicate intentional concealment. This represents a serious security and privacy risk and should be flagged as high severity malware.

Live on npm for 3 days, 8 hours and 43 minutes before removal. Socket users were protected even while the package was live.

The script 'packer/provisioners/post_install.sh' exhibits malicious behavior by performing several harmful actions: - **Deletes user and root history files**: Uses secure deletion methods to remove history files, potentially to conceal malicious activities. - **Clears system log files**: Erases log files from '/var/log', hindering the ability to audit and investigate system actions. - **Disables the root account**: Locks the root account password without ensuring alternative secure administrative access, possibly preventing legitimate administrative operations. - **Sets a weak default password ('changeme') for the 'admin' user**: Introduces a significant security risk by using an easily guessable password, facilitating unauthorized access. These actions can be exploited by an attacker to gain unauthorized access, disrupt legitimate operations, and prevent system recovery. The combination of log and history deletion, disabling of root access, and setting weak credentials indicates malicious intent to compromise system security and conceal nefarious activities.

This code poses a serious security risk and should not be used.

Live on npm for 40 minutes before removal. Socket users were protected even while the package was live.

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as protestware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The code is exfiltrating environment variables to an external server, which is a serious security concern. This action is indicative of data theft and should be considered malicious.

Live on npm for 5 hours and 57 minutes before removal. Socket users were protected even while the package was live.

The code poses a potential security risk due to the execution of `sendSystemData`, which may send system data over the network. The dynamic modification of package files is also suspicious. Further investigation into the `collector` module is necessary to determine the exact nature of `sendSystemData`.

Live on npm for 9 hours and 16 minutes before removal. Socket users were protected even while the package was live.

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.

The code poses a significant security risk as it writes and executes an unknown executable with elevated privileges. This behavior is consistent with malicious activities and could lead to unauthorized actions on the system.

Live on npm for 2 hours and 32 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it collects and transmits sensitive user data to an external server without consent, posing a significant risk to user privacy and security.

Live on npm for 19 days, 19 hours and 27 minutes before removal. Socket users were protected even while the package was live.

This code collects extensive system information and sends it to a hardcoded Slack webhook URL. This behavior is suspicious as it constitutes data exfiltration. The presence of a hardcoded URL and the collection of sensitive information such as user details, filesystem info, and network interfaces indicate potentially malicious intent.

This file decodes and immediately executes an obfuscated payload that imports fs, os, child_process, https, and path. It performs an HTTPS GET to https://mainnet[.]unstoppableapi[.]xyz/v2/id=2199046105100425&secret=iREMmhXBnAwk, writes the response into a temporary script (replacing .ps1 with .vbs on Windows), and then spawns a detached shell process with execution-policy bypass (PowerShell.exe) or nohup (wscript.exe/osascript/bash) to run the downloaded code without user consent. All operations silence output (ignore stdio) and suppress errors, indicating a backdoor or downloader behavior that poses a critical supply-chain security risk.

The code contains highly suspicious behavior likely indicative of a backdoor, including fetching and executing shell commands from a hard-coded IP address upon instantiation of the Client class. This behavior poses a severe security risk.

Live on npm for 5 hours and 33 minutes before removal. Socket users were protected even while the package was live.

This package is malicious in nature, embedding explicit adult content and suspicious external links within what should be source code. It does not contain legitimate software logic and is likely a supply chain compromise used to distribute spam or malware. The provided reports are invalid and do not analyze the content. The package should be rejected and blacklisted due to high malware and security risk scores.

This is clearly malicious code implementing a supply chain attack. It loads and executes arbitrary JavaScript from a typosquatting domain, particularly when initial validation fails. The code uses obfuscation techniques and represents a serious security threat.

Live on npm for 4 hours and 41 minutes before removal. Socket users were protected even while the package was live.

The package 'node-webcam@0.8.2' includes a post-installation script that downloads an executable file ('CommandCam.exe') from an external source without validation or integrity checks. Specifically, when installed on Windows systems, the script retrieves 'CommandCam.exe' from 'https://github[.]com/chuckfairy/node-webcam/releases/download/v0.6/CommandCam.exe' and saves it to 'src/bindings/CommandCam/CommandCam.exe' without obtaining user consent. CommandCam.exe (SHA256: 012d3ff83b1e65182807512fc9d04bcfdb40736fcdc2f7aba57531cbf031769e) is flagged as malicious by 22 out of 71 security vendors on VirusTotal. Downloading and executing binaries from external sources without validation introduces a security vulnerability, as the external source could be compromised to deliver malicious code, leading to potential arbitrary code execution on the user's system.

This code is highly suspicious and should not be used without further investigation. The code is heavily obfuscated and could potentially contain malicious code. The purpose of the code is unclear and further investigation is necessary to determine its exact behavior.

Live on npm for 12 minutes before removal. Socket users were protected even while the package was live.

The code exhibits malicious behavior by collecting and transmitting sensitive system information to a suspicious domain without user consent. This poses a significant security risk.

Live on npm for 4 days, 2 hours and 37 minutes before removal. Socket users were protected even while the package was live.

The code collects sensitive system information without user consent and sends it to an external server via a Discord webhook. The code gathers data such as the user's internal IP address, external IP address (obtained via an HTTP request to 'https[:]//ipinfo[.]io/json'), hostname, username, home directory, DNS server information, and package details from 'package.json'. This information is then formatted into a JSON object and transmitted to a hardcoded Discord webhook URL ('https[:]//discord[.]com/api/webhooks/...'). This behavior constitutes unauthorized data exfiltration and poses significant privacy and security risks.

Live on npm for 15 days, 2 hours and 35 minutes before removal. Socket users were protected even while the package was live.

This code exhibits behavior consistent with data exfiltration, employing both direct HTTP(S) transmission and covert DNS queries as a fallback mechanism. The obfuscation, target domain, and sophisticated fallback mechanism significantly raise suspicions of malicious intent.

Live on npm for 4 minutes before removal. Socket users were protected even while the package was live.

The script poses a high security risk as malware due to its ability to alter disk partitions without user interaction, leading to data loss or system damage.

The code exhibits behavior consistent with potential malware, as it decodes and executes an unknown binary with elevated privileges. This poses a significant security risk.

Live on npm for 13 days, 21 hours and 10 minutes before removal. Socket users were protected even while the package was live.

The code is indeed malicious, performing potentially harmful activities such as gathering system information and sending it to an external server via DNS requests. It poses a serious security risk due to its potential for data exfiltration.

Live on npm for 7 minutes before removal. Socket users were protected even while the package was live.

Possible typosquat of azure - Explanation: The package 'azure-graphrbac' is labeled as a 'security holding package', which often indicates a placeholder to prevent typosquatting. The name 'azure-graphrbac' closely resembles legitimate Azure package naming conventions, which could confuse users. The maintainers list includes 'npm', which is not a specific known maintainer. Therefore, it is likely a typosquat.

Live on npm for 2 hours and 28 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it covertly collects and transmits sensitive system and user environment data to an external endpoint without consent. This constitutes data exfiltration and poses a high security risk. The code is straightforward and not obfuscated, but the intent and effect are clearly malicious. It should be flagged and avoided.

Live on npm for 2 hours and 37 minutes before removal. Socket users were protected even while the package was live.

The code exhibits behavior characteristic of malware, including the collection of sensitive data, use of obfuscation, and execution of potentially arbitrary code using eval. The intentional obfuscation and disabling of NODE_NO_EVAL are indicative of an attempt to hide malicious behavior and enable unsafe operations.

Live on npm for 1 hour and 33 minutes before removal. Socket users were protected even while the package was live.

This source code is malicious. It performs stealthy data exfiltration of sensitive system and environment information to a suspicious hardcoded IP address. The evasion techniques and randomized network behavior indicate intentional concealment. This represents a serious security and privacy risk and should be flagged as high severity malware.

Live on npm for 3 days, 8 hours and 43 minutes before removal. Socket users were protected even while the package was live.

The script 'packer/provisioners/post_install.sh' exhibits malicious behavior by performing several harmful actions: - **Deletes user and root history files**: Uses secure deletion methods to remove history files, potentially to conceal malicious activities. - **Clears system log files**: Erases log files from '/var/log', hindering the ability to audit and investigate system actions. - **Disables the root account**: Locks the root account password without ensuring alternative secure administrative access, possibly preventing legitimate administrative operations. - **Sets a weak default password ('changeme') for the 'admin' user**: Introduces a significant security risk by using an easily guessable password, facilitating unauthorized access. These actions can be exploited by an attacker to gain unauthorized access, disrupt legitimate operations, and prevent system recovery. The combination of log and history deletion, disabling of root access, and setting weak credentials indicates malicious intent to compromise system security and conceal nefarious activities.

This code poses a serious security risk and should not be used.

Live on npm for 40 minutes before removal. Socket users were protected even while the package was live.