Secure your dependencies. Ship with confidence.

The code engages in potentially malicious behavior by collecting sensitive system information and sending it to a remote server without clear user consent. The hard-coded domain, data obfuscation, and lack of transparency raise significant privacy and security concerns. The risk score is high due to the invasive nature of the code.

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

The code exhibits several serious security issues, including disabling TLS validation, collecting and sending sensitive system and user information to a remote server without user consent, and disabling Node.js warnings. These actions indicate a high probability of malicious intent and pose significant security risks.

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

The code collects sensitive system information (environment variables, hostname, network interfaces) and sends it to an external server without user consent. This behavior is indicative of data exfiltration and poses a significant security risk.

The code is designed to collect sensitive system information and transmit it to an external server using obfuscated methods. This behavior is indicative of malicious activity, specifically data exfiltration.

Live on npm for 21 minutes 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 appears to be collecting sensitive system information and sending it to an external server. This behavior is indicative of data theft. Additionally, the reference to buying something through Telegram is highly suspicious and suggests potential malicious intent. Overall, this code poses a significant security risk.

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

The code exhibits potential malicious behavior with data exfiltration and tracking activities, posing a significant security risk. It should be further investigated and potentially removed.

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

The code sends tracking data over HTTPS to a remote server, but it sends potentially sensitive information without clear user consent or notification. The purpose of tracking user data should be clearly stated and user consent should be obtained before collecting and sending any data. Additionally, the destination of the data is an external server and should be verified as trusted. Overall, the code poses a potential privacy concern for some users and should be used with caution.

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

The code presents significant privacy risks and potential for misuse in generating fake identities, which is indicative of malicious intent. The scraping of sensitive information from a third-party website without clear user consent is highly suspicious.

Live on pypi for 17 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.

Possible typosquat of [azure](https://socket.dev/npm/package/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 'azure' and could be misleading. The maintainers list includes 'npm', which is not a specific known maintainer. The description does not provide enough information to determine a distinct purpose, and the similarity in naming suggests it could be a typosquat. azure-graphrbac is a security-holding package

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

The source code is malicious as it collects and sends sensitive system information to a remote server using obfuscated code. The behavior is consistent with data exfiltration techniques, and the obfuscation further indicates an attempt to hide these activities.

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

This script makes an HTTP request to an external source, which could be used for data exfiltration or to fetch malicious content. This behavior is highly suspicious.

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

This script is highly suspicious and potentially malicious. It downloads a file from an external source and executes it with elevated privileges in the background. This behavior can lead to unauthorized code execution and system compromise.

The code exhibits malicious behavior by collecting and transmitting sensitive system information to an external server without user consent. This poses a high security risk and potential for data theft.

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

The script is designed to send sensitive information to a remote server, which poses a significant security risk and indicates malicious intent.

The code is designed to collect and send sensitive information to a remote server without the user's knowledge or consent. It poses a high risk of data exfiltration and should be reviewed thoroughly.

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

This command creates a reverse shell to the IP address '13.126.64.224' on port '56764'. This is a clear indication of malicious intent and should be considered a high security risk.

The code is heavily obfuscated and uses dynamic code execution, which raises concerns about potential malicious behavior. Without further deobfuscation, it is difficult to determine the exact functionality or intent. The lack of detailed reports further complicates the analysis.

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

The code engages in automated package creation and publishing, with the addition of posting content to WordPress sites using hard-coded credentials. This indicates potential spam or automated SEO manipulation behavior. The code also presents significant security risks due to hard-coded paths and credentials.

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

The code is suspicious and likely malicious, as it collects sensitive system information and sends it over DNS queries to an external domain. This behavior is indicative of data exfiltration. The disabling of TLS validation further increases the security risk.

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

The source code is designed to exfiltrate sensitive system information to a remote server without user consent. This behavior is indicative of malicious intent, posing a significant security risk.

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

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.

Possible `1-step D-L dist` typosquat of [body-parser](https://socket.dev/npm/package/body-parser) Explanation: The package 'bodyfpvarser' is a security holding package with a name very similar to 'body-parser', which suggests it could be a typosquat. The description 'security holding package' indicates it is not intended for actual use, but the similarity in name raises suspicion. The maintainers list includes 'npm', which is not a specific known maintainer, adding to the suspicion. Security holding package. Closed as malware.

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

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

The code engages in potentially malicious behavior by collecting sensitive system information and sending it to a remote server without clear user consent. The hard-coded domain, data obfuscation, and lack of transparency raise significant privacy and security concerns. The risk score is high due to the invasive nature of the code.

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

The code exhibits several serious security issues, including disabling TLS validation, collecting and sending sensitive system and user information to a remote server without user consent, and disabling Node.js warnings. These actions indicate a high probability of malicious intent and pose significant security risks.

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

The code collects sensitive system information (environment variables, hostname, network interfaces) and sends it to an external server without user consent. This behavior is indicative of data exfiltration and poses a significant security risk.

The code is designed to collect sensitive system information and transmit it to an external server using obfuscated methods. This behavior is indicative of malicious activity, specifically data exfiltration.

Live on npm for 21 minutes 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 appears to be collecting sensitive system information and sending it to an external server. This behavior is indicative of data theft. Additionally, the reference to buying something through Telegram is highly suspicious and suggests potential malicious intent. Overall, this code poses a significant security risk.

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

The code exhibits potential malicious behavior with data exfiltration and tracking activities, posing a significant security risk. It should be further investigated and potentially removed.

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

The code sends tracking data over HTTPS to a remote server, but it sends potentially sensitive information without clear user consent or notification. The purpose of tracking user data should be clearly stated and user consent should be obtained before collecting and sending any data. Additionally, the destination of the data is an external server and should be verified as trusted. Overall, the code poses a potential privacy concern for some users and should be used with caution.

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

The code presents significant privacy risks and potential for misuse in generating fake identities, which is indicative of malicious intent. The scraping of sensitive information from a third-party website without clear user consent is highly suspicious.

Live on pypi for 17 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.

Possible typosquat of [azure](https://socket.dev/npm/package/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 'azure' and could be misleading. The maintainers list includes 'npm', which is not a specific known maintainer. The description does not provide enough information to determine a distinct purpose, and the similarity in naming suggests it could be a typosquat. azure-graphrbac is a security-holding package

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

The source code is malicious as it collects and sends sensitive system information to a remote server using obfuscated code. The behavior is consistent with data exfiltration techniques, and the obfuscation further indicates an attempt to hide these activities.

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

This script makes an HTTP request to an external source, which could be used for data exfiltration or to fetch malicious content. This behavior is highly suspicious.

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

This script is highly suspicious and potentially malicious. It downloads a file from an external source and executes it with elevated privileges in the background. This behavior can lead to unauthorized code execution and system compromise.

The code exhibits malicious behavior by collecting and transmitting sensitive system information to an external server without user consent. This poses a high security risk and potential for data theft.

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

The script is designed to send sensitive information to a remote server, which poses a significant security risk and indicates malicious intent.

The code is designed to collect and send sensitive information to a remote server without the user's knowledge or consent. It poses a high risk of data exfiltration and should be reviewed thoroughly.

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

This command creates a reverse shell to the IP address '13.126.64.224' on port '56764'. This is a clear indication of malicious intent and should be considered a high security risk.

The code is heavily obfuscated and uses dynamic code execution, which raises concerns about potential malicious behavior. Without further deobfuscation, it is difficult to determine the exact functionality or intent. The lack of detailed reports further complicates the analysis.

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

The code engages in automated package creation and publishing, with the addition of posting content to WordPress sites using hard-coded credentials. This indicates potential spam or automated SEO manipulation behavior. The code also presents significant security risks due to hard-coded paths and credentials.

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

The code is suspicious and likely malicious, as it collects sensitive system information and sends it over DNS queries to an external domain. This behavior is indicative of data exfiltration. The disabling of TLS validation further increases the security risk.

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

The source code is designed to exfiltrate sensitive system information to a remote server without user consent. This behavior is indicative of malicious intent, posing a significant security risk.

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

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.

Possible `1-step D-L dist` typosquat of [body-parser](https://socket.dev/npm/package/body-parser) Explanation: The package 'bodyfpvarser' is a security holding package with a name very similar to 'body-parser', which suggests it could be a typosquat. The description 'security holding package' indicates it is not intended for actual use, but the similarity in name raises suspicion. The maintainers list includes 'npm', which is not a specific known maintainer, adding to the suspicion. Security holding package. Closed as malware.

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

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