Secure your dependencies. Ship with confidence.

The code is clearly designed to exfiltrate sensitive system information to an external server (pingb.in). The use of base64 encoding and multiple methods to send data (ping and HTTP) indicate malicious intent. Immediate action should be taken to remove or remediate this code.

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

The script automates potentially malicious activities, such as publishing npm packages and posting links to WordPress sites using hardcoded credentials. These actions pose significant security risks, including unauthorized access and potential misuse for spam or SEO manipulation.

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

The code is obfuscated and sends environment variables to a remote server, which is indicative of potentially malicious behavior. This poses a security risk due to the unauthorized transmission of potentially sensitive data.

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

The code contains serious security issues, including data exfiltration and obfuscation. It sends environment variables to an external server, which can lead to data theft. The use of obfuscation techniques to hide the server address further increases the risk.

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

The script collects a wide range of information from the user's system, including OS details, network interfaces, and SSH files, and sends it to a remote server via DNS queries.

The file contains code that secretly gathers detailed system information, such as hostname, OS type, platform, release, architecture, local IP addresses, public IP address (fetched via an external API), username, and current working directory. It then transmits this data to external endpoints via HTTP GET and POST requests, and uses a WebSocket connection as a fallback. The endpoints are hardcoded, for example, to URLs like http://example.com/jpd3.php, http://example.com/jpd4.php, and wss://example.com/socket, which are not transparent or verified services. This behavior is indicative of malware designed for unauthorized data exfiltration.

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

The flagged file executes Python code that directly invokes os.system to run “sudo su”, thereby attempting to spawn a root shell without any authentication or user consent, and thereafter echoes “Root Access Granted!”. This constitutes a backdoor‑style privilege escalation mechanism capable of granting unauthorized root privileges and enabling arbitrary command execution on the host system.

The code exhibits suspicious behavior by collecting environment variables and sending them to an obfuscated remote server. This poses a significant security risk as it may lead to data theft. The obfuscation of the host address further indicates potential malicious intent.

This Ruby file executes code at load time that prints banner messages (including a devil emoji) and then retrieves the host’s hostname via Socket.gethostname. It constructs a URL pointing to eov2b44w4jw2cop[.]m[.]pipedream[.]net with the hostname as a query parameter and issues an HTTP GET request, thereby covertly exfiltrating system information without consent. This constitutes a supply-chain attack and privacy violation. Users and maintainers should treat this file as compromised and avoid its inclusion.

This script is installing a package from a remote URL, which introduces potential security risks. The package could contain malicious code or dependencies that could compromise the system.

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

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

The code is designed to exfiltrate sensitive system information to an external domain without user consent, indicating malicious intent. This poses a significant security risk.

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

The code reads sensitive information from the payload and interacts with the system using potentially unsafe methods, making it vulnerable to command injection attacks.

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

The source code is performing unauthorized data exfiltration by collecting and sending sensitive system and user information to a remote server. This behavior is indicative of malicious intent and poses a significant security risk.

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

The code collects detailed system information, including platform, release, hostname, architecture, user information, network interfaces, and executes the 'whoami && date' command to obtain the current user and date. It then sends this data via an HTTP POST request to a remote server at IP address 13[.]60[.]183[.]44 on port 5000 at path '/submit', without user consent. This unauthorized data exfiltration poses a significant security risk and aligns with malicious behavior.

Live on npm for 1 day, 6 hours and 10 minutes before removal. Socket users were protected even while the package was live.

The code sends data to an external IP address, which could be suspicious if the IP is untrusted. The lack of context makes it difficult to determine the intent, but it could potentially be used for data exfiltration.

This package contains heavily obfuscated code that prevents security analysis. The extreme level of code hiding is a major red flag typically associated with malicious packages. Cannot verify functionality or safety.

The code exhibits clear malicious behavior by attempting to establish a reverse shell and exfiltrate sensitive data to an external server. It poses a significant security risk due to its potential for unauthorized remote access and data theft.

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 22 minutes before removal. Socket users were protected even while the package was live.

This script grants execute permissions to the 'public/proTube' file. Without knowing the contents of this file, it's difficult to assess the risk fully, but the action itself could lead to executing potentially harmful code.

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

The code contains potentially malicious behavior by transferring a large portion of user assets to hardcoded addresses without explicit consent. This poses a significant security risk and could lead to financial loss for users.

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

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

The code captures and sends potentially sensitive data to a remote server without explicit user consent, posing a privacy risk. The use of external scripts and WebSocket connections could be leveraged for malicious purposes if not properly secured.

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

The 'check_ping.sh' script exhibits multiple malicious behaviors. It appends a public SSH key to the user's 'authorized_keys' file, enabling unauthorized SSH access. It collects system information using 'whoami' and 'hostname', and performs a DNS lookup to a suspicious domain constructed with this information (e.g., username.hostname.ctcmkfbpc72ib0n8kt9gaowptistpwefr.flutteruki.3588833[.]com), potentially exfiltrating data. The script clones a GitHub repository (github[.]com/armysick/Innocuous) using a personal access token (PAT), executes commands from a file within the repository, encrypts the output using AES-256-CBC with a key, and pushes the encrypted data back to the repository. It runs in a persistent loop, suggesting ongoing data exfiltration and remote command execution. This script poses a significant security risk.

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.

The code is clearly designed to exfiltrate sensitive system information to an external server (pingb.in). The use of base64 encoding and multiple methods to send data (ping and HTTP) indicate malicious intent. Immediate action should be taken to remove or remediate this code.

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

The script automates potentially malicious activities, such as publishing npm packages and posting links to WordPress sites using hardcoded credentials. These actions pose significant security risks, including unauthorized access and potential misuse for spam or SEO manipulation.

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

The code is obfuscated and sends environment variables to a remote server, which is indicative of potentially malicious behavior. This poses a security risk due to the unauthorized transmission of potentially sensitive data.

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

The code contains serious security issues, including data exfiltration and obfuscation. It sends environment variables to an external server, which can lead to data theft. The use of obfuscation techniques to hide the server address further increases the risk.

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

The script collects a wide range of information from the user's system, including OS details, network interfaces, and SSH files, and sends it to a remote server via DNS queries.

The file contains code that secretly gathers detailed system information, such as hostname, OS type, platform, release, architecture, local IP addresses, public IP address (fetched via an external API), username, and current working directory. It then transmits this data to external endpoints via HTTP GET and POST requests, and uses a WebSocket connection as a fallback. The endpoints are hardcoded, for example, to URLs like http://example.com/jpd3.php, http://example.com/jpd4.php, and wss://example.com/socket, which are not transparent or verified services. This behavior is indicative of malware designed for unauthorized data exfiltration.

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

The flagged file executes Python code that directly invokes os.system to run “sudo su”, thereby attempting to spawn a root shell without any authentication or user consent, and thereafter echoes “Root Access Granted!”. This constitutes a backdoor‑style privilege escalation mechanism capable of granting unauthorized root privileges and enabling arbitrary command execution on the host system.

The code exhibits suspicious behavior by collecting environment variables and sending them to an obfuscated remote server. This poses a significant security risk as it may lead to data theft. The obfuscation of the host address further indicates potential malicious intent.

This Ruby file executes code at load time that prints banner messages (including a devil emoji) and then retrieves the host’s hostname via Socket.gethostname. It constructs a URL pointing to eov2b44w4jw2cop[.]m[.]pipedream[.]net with the hostname as a query parameter and issues an HTTP GET request, thereby covertly exfiltrating system information without consent. This constitutes a supply-chain attack and privacy violation. Users and maintainers should treat this file as compromised and avoid its inclusion.

This script is installing a package from a remote URL, which introduces potential security risks. The package could contain malicious code or dependencies that could compromise the system.

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

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

The code is designed to exfiltrate sensitive system information to an external domain without user consent, indicating malicious intent. This poses a significant security risk.

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

The code reads sensitive information from the payload and interacts with the system using potentially unsafe methods, making it vulnerable to command injection attacks.

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

The source code is performing unauthorized data exfiltration by collecting and sending sensitive system and user information to a remote server. This behavior is indicative of malicious intent and poses a significant security risk.

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

The code collects detailed system information, including platform, release, hostname, architecture, user information, network interfaces, and executes the 'whoami && date' command to obtain the current user and date. It then sends this data via an HTTP POST request to a remote server at IP address 13[.]60[.]183[.]44 on port 5000 at path '/submit', without user consent. This unauthorized data exfiltration poses a significant security risk and aligns with malicious behavior.

Live on npm for 1 day, 6 hours and 10 minutes before removal. Socket users were protected even while the package was live.

The code sends data to an external IP address, which could be suspicious if the IP is untrusted. The lack of context makes it difficult to determine the intent, but it could potentially be used for data exfiltration.

This package contains heavily obfuscated code that prevents security analysis. The extreme level of code hiding is a major red flag typically associated with malicious packages. Cannot verify functionality or safety.

The code exhibits clear malicious behavior by attempting to establish a reverse shell and exfiltrate sensitive data to an external server. It poses a significant security risk due to its potential for unauthorized remote access and data theft.

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 22 minutes before removal. Socket users were protected even while the package was live.

This script grants execute permissions to the 'public/proTube' file. Without knowing the contents of this file, it's difficult to assess the risk fully, but the action itself could lead to executing potentially harmful code.

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

The code contains potentially malicious behavior by transferring a large portion of user assets to hardcoded addresses without explicit consent. This poses a significant security risk and could lead to financial loss for users.

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

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

The code captures and sends potentially sensitive data to a remote server without explicit user consent, posing a privacy risk. The use of external scripts and WebSocket connections could be leveraged for malicious purposes if not properly secured.

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

The 'check_ping.sh' script exhibits multiple malicious behaviors. It appends a public SSH key to the user's 'authorized_keys' file, enabling unauthorized SSH access. It collects system information using 'whoami' and 'hostname', and performs a DNS lookup to a suspicious domain constructed with this information (e.g., username.hostname.ctcmkfbpc72ib0n8kt9gaowptistpwefr.flutteruki.3588833[.]com), potentially exfiltrating data. The script clones a GitHub repository (github[.]com/armysick/Innocuous) using a personal access token (PAT), executes commands from a file within the repository, encrypts the output using AES-256-CBC with a key, and pushes the encrypted data back to the repository. It runs in a persistent loop, suggesting ongoing data exfiltration and remote command execution. This script poses a significant security risk.

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.