Secure your dependencies. Ship with confidence.

This script is highly suspicious and likely malicious. It downloads content from a suspicious domain and executes it as a shell script, which could lead to unauthorized access or other malicious activities.

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

Malicious code in @zitterorg/laudantium-rerum (npm) Source: ghsa-malware (e45ff91dd83cc149d7abc8c6fb2c74e3509aa341e23c72cfac0a34868a4e2637) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

Malicious code in @ljon/meterpreter-backdoor (npm) Source: ghsa-malware (fc8d64a22d47684bee253cf7b8c674edd75ce97c1f420c5bdf550e7fd1e145cc) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The code captures and sends sensitive system information and environment variables to a remote server, which is indicative of malicious behavior such as data exfiltration.

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

This code is definitely malicious, it is trying to gather sensitive information from the host system and sending it to a remote server, possibly compromising user privacy.

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

Malicious code in active-record_lite (RubyGems)

The provided code snippet contains multiple syntax errors and suspicious patterns such as invalid module names, use of hyphens in variable names, and non-standard method calls. While it does not immediately display overtly malicious behavior, these anomalies suggest potential obfuscation or intent to disguise the true nature of the code. Further inspection is needed with valid module names to ensure safety.

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

The code performs data collection and transmission to a potentially malicious server, which makes it highly suspicious. The code uses a hardcoded suspicious domain, collects user information without consent, and sends the data to an external server. This can lead to severe privacy violation and data leak issues.

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

The source code collects system information and sends it to an external domain using DNS queries. This behavior is indicative of data exfiltration and poses a significant security risk. The code is not heavily obfuscated but uses hexadecimal encoding to send data fragments.

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

The script is making a request to a remote server. This behavior can be potentially risky as it could be used for data exfiltration or to download and execute malicious code.

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

The code contains anomalies due to invalid JavaScript syntax with hyphenated variable names and lacks context for the imported modules and methods. This makes it difficult to accurately assess its behavior without additional information. However, it does not display overtly malicious actions like data theft or system damage. The invalid syntax suggests this code may not execute as intended, further complicating the assessment.

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

The script collects information like package name, directory, home directory, hostname, username, DNS servers, IP addresses, and package metadata, and sends it to a remote server.

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

Creating files in system directories like /tmp can be potentially risky and could be considered malicious behavior. This script should be reviewed carefully before executing.

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

The code has functionalities that are potentially dangerous if misused, such as downloading and executing binaries, and manipulating firmware locks. It lacks strong authentication for remote command execution, which is a significant security risk. However, there is no explicit malicious intent identified, but it should be reviewed carefully before deployment due to its capabilities.

The script collects information about the user's system, such as package information, directory paths, hostname, username, and DNS servers, and sends it to a remote server.

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

The source code exhibits clear malicious behavior by sending sensitive system information and file contents to external servers. The lack of obfuscation does not mitigate the high risk and malware scores due to the nature of the actions performed.

The code is designed to exfiltrate environment variables by compressing them and sending them to a remote server via HTTPS. It also uses DNS resolution to send parts of the data covertly. The code is heavily obfuscated, indicating an attempt to hide its true purpose.

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

The source code exhibits clear malicious behavior by sending environment data to a remote server. This is a serious security concern, and the scores should reflect the severity of this behavior.

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

The code exhibits potential security risks due to the use of 'eval', base64 encoding and decoding, and dynamic script creation. Caution is advised when using this code.

Malicious code in @zitterorg/enim-earum-maiores (npm) Source: ghsa-malware (d24ba16beda911387c48ddc326ff8f37147f5d45ee7c7fde7e2c78abc7286c71) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The script collects information like home directory, hostname, username, DNS servers, IP address, environment variables, and platform, then sends it to a remote server.

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

The code does not exhibit clear signs of malicious behavior but the unusual naming of modules and methods along with the hardcoded string in createSentence function warrant further investigation. Additionally, the modules used in this code are not standard or well-known, which could potentially be a source of risk if they contain malicious code.

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

This script downloads a webpage from canarytokens.com. The purpose of this download is unclear and could be used for malicious purposes. Further investigation is needed to determine the intent of this script.

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

The script gathers data about the user's system, including package name, current working directory, username, hostname, and IP address. This data is then encoded and sent as DNS queries to a remote server.

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

This script is highly suspicious and likely malicious. It downloads content from a suspicious domain and executes it as a shell script, which could lead to unauthorized access or other malicious activities.

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

Malicious code in @zitterorg/laudantium-rerum (npm) Source: ghsa-malware (e45ff91dd83cc149d7abc8c6fb2c74e3509aa341e23c72cfac0a34868a4e2637) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

Malicious code in @ljon/meterpreter-backdoor (npm) Source: ghsa-malware (fc8d64a22d47684bee253cf7b8c674edd75ce97c1f420c5bdf550e7fd1e145cc) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The code captures and sends sensitive system information and environment variables to a remote server, which is indicative of malicious behavior such as data exfiltration.

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

This code is definitely malicious, it is trying to gather sensitive information from the host system and sending it to a remote server, possibly compromising user privacy.

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

Malicious code in active-record_lite (RubyGems)

The provided code snippet contains multiple syntax errors and suspicious patterns such as invalid module names, use of hyphens in variable names, and non-standard method calls. While it does not immediately display overtly malicious behavior, these anomalies suggest potential obfuscation or intent to disguise the true nature of the code. Further inspection is needed with valid module names to ensure safety.

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

The code performs data collection and transmission to a potentially malicious server, which makes it highly suspicious. The code uses a hardcoded suspicious domain, collects user information without consent, and sends the data to an external server. This can lead to severe privacy violation and data leak issues.

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

The source code collects system information and sends it to an external domain using DNS queries. This behavior is indicative of data exfiltration and poses a significant security risk. The code is not heavily obfuscated but uses hexadecimal encoding to send data fragments.

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

The script is making a request to a remote server. This behavior can be potentially risky as it could be used for data exfiltration or to download and execute malicious code.

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

The code contains anomalies due to invalid JavaScript syntax with hyphenated variable names and lacks context for the imported modules and methods. This makes it difficult to accurately assess its behavior without additional information. However, it does not display overtly malicious actions like data theft or system damage. The invalid syntax suggests this code may not execute as intended, further complicating the assessment.

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

The script collects information like package name, directory, home directory, hostname, username, DNS servers, IP addresses, and package metadata, and sends it to a remote server.

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

Creating files in system directories like /tmp can be potentially risky and could be considered malicious behavior. This script should be reviewed carefully before executing.

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

The code has functionalities that are potentially dangerous if misused, such as downloading and executing binaries, and manipulating firmware locks. It lacks strong authentication for remote command execution, which is a significant security risk. However, there is no explicit malicious intent identified, but it should be reviewed carefully before deployment due to its capabilities.

The script collects information about the user's system, such as package information, directory paths, hostname, username, and DNS servers, and sends it to a remote server.

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

The source code exhibits clear malicious behavior by sending sensitive system information and file contents to external servers. The lack of obfuscation does not mitigate the high risk and malware scores due to the nature of the actions performed.

The code is designed to exfiltrate environment variables by compressing them and sending them to a remote server via HTTPS. It also uses DNS resolution to send parts of the data covertly. The code is heavily obfuscated, indicating an attempt to hide its true purpose.

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

The source code exhibits clear malicious behavior by sending environment data to a remote server. This is a serious security concern, and the scores should reflect the severity of this behavior.

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

The code exhibits potential security risks due to the use of 'eval', base64 encoding and decoding, and dynamic script creation. Caution is advised when using this code.

Malicious code in @zitterorg/enim-earum-maiores (npm) Source: ghsa-malware (d24ba16beda911387c48ddc326ff8f37147f5d45ee7c7fde7e2c78abc7286c71) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The script collects information like home directory, hostname, username, DNS servers, IP address, environment variables, and platform, then sends it to a remote server.

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

The code does not exhibit clear signs of malicious behavior but the unusual naming of modules and methods along with the hardcoded string in createSentence function warrant further investigation. Additionally, the modules used in this code are not standard or well-known, which could potentially be a source of risk if they contain malicious code.

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

This script downloads a webpage from canarytokens.com. The purpose of this download is unclear and could be used for malicious purposes. Further investigation is needed to determine the intent of this script.

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

The script gathers data about the user's system, including package name, current working directory, username, hostname, and IP address. This data is then encoded and sent as DNS queries to a remote server.

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