Secure your dependencies. Ship with confidence.

The script is designed to exfiltrate sensitive system information to an external server via DNS queries. The use of obfuscation and the method of data transmission indicate malicious intent.

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

Malicious code in @azure-tests/perf-storage-file-share-track-1 (npm) Source: ghsa-malware (a77a70aec760d01762f6eea825194c2d558174a44b966b59043ce3f9424626f0) 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.

Malicious code in bitpay-cordova-sdk (npm) Source: ghsa-malware (c65a1f5a2711ae665b870cf63ffa85839dffa1c1acff19b1dad0fc07233dd05b) 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.

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

The script collects information like current working directory, hostname, username, and home directory and sends it to a remote server.

This script is highly suspicious and potentially malicious. It is attempting to exfiltrate system information and send it to a Telegram bot. This poses a significant security risk.

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

Malicious code in coinmarketcap.com (npm) Source: ghsa-malware (cb95c3bffb062ee135c99ebd88cf1ed249f2d70dfb23f5b24477d3cc4fa471ea) 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.

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

The code fetches and potentially exposes sensitive authorization information in an insecure manner from Pastebin, which is a red flag for data security and integrity.

Malicious code in typeahead-client-logger (npm) Source: ghsa-malware (9121846b93247c8f8db2f98b553de9231e63282325f9bbaff65e8b6916d2a6cf) 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.

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

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

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.

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

Malicious code in frogsui (npm) Source: ghsa-malware (9baef0dc09c1323da3d13f47bc554883c6d7d3cee1c9afe05b9dbe94615b3939) 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.

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

Malicious code in @w3-commons/js-build-resources (npm) Source: ghsa-malware (7872915f84a85c03dfe50e7b7cef0787845ceaad3aac20ea1c20b7a844eb01e1) 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 seems to be suspicious as it reads system information and sends it to a remote server without a clear purpose. The presence of a hardcoded remote server address and the lack of user consent raise concerns about the intent of the code. Additionally, the 'debugger' keyword suggests that the code may have been used for debugging purposes and should not be present in production code.

The code snippet is highly obfuscated, making it difficult to ascertain its true intent or potential security risks. Without proper documentation or context, it is challenging to determine if there are any malicious behaviors present. Therefore, the security risk and malware likelihood cannot be definitively assessed.

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

Malicious code in curri-slack (npm) Source: ghsa-malware (a00fcf2aed2ef83f63aa909e95ceaeba67a19ae3189fe65bda5debdb8856e229) 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.

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

The code is highly suspicious and potentially malicious. It collects system information and sends it to a third-party site via DNS requests, which could be used for data exfiltration or tracking. It is recommended to avoid using this package due to the high security risk it poses.

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

Malicious code in azure-template-samples-ts-beta (npm) Source: ghsa-malware (b10d6fbf59581245f9918f3edb36dbc7879dee46d5b4d15555e411f29da0cf76) 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.

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

Malicious code in usaa-typography (npm) Source: ghsa-malware (5c459f6f99ba8293610148243ff44fd4b6810f70dcb75441158c134021cb7e95) 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.

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

Malicious code in brave-core-crx-packager (npm) Source: ghsa-malware (9d659bff6641ae2eba134b7096de9c5134287f99bb6aad5396c9f30be533d099) 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.

Malicious code in azure-arm-postgresql-flexible-samples-js (npm) Source: ghsa-malware (c67780d0043880a352f0f1137b729e497fa946b957fae4ca0f72384df954fa8e) 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.

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

The code poses a significant privacy risk as it captures and sends desktop screenshots without explicit user consent. The destination of the data is unknown, raising concerns about potential data theft or unauthorized surveillance.

Malicious code in body-complex (npm) Source: ghsa-malware (ef48c53ad39055a3692dbe528815988861df665507cc31c52dad47e5f746b3e3) 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.

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

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

The script is designed to exfiltrate sensitive system information to an external server via DNS queries. The use of obfuscation and the method of data transmission indicate malicious intent.

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

Malicious code in @azure-tests/perf-storage-file-share-track-1 (npm) Source: ghsa-malware (a77a70aec760d01762f6eea825194c2d558174a44b966b59043ce3f9424626f0) 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.

Malicious code in bitpay-cordova-sdk (npm) Source: ghsa-malware (c65a1f5a2711ae665b870cf63ffa85839dffa1c1acff19b1dad0fc07233dd05b) 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.

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

The script collects information like current working directory, hostname, username, and home directory and sends it to a remote server.

This script is highly suspicious and potentially malicious. It is attempting to exfiltrate system information and send it to a Telegram bot. This poses a significant security risk.

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

Malicious code in coinmarketcap.com (npm) Source: ghsa-malware (cb95c3bffb062ee135c99ebd88cf1ed249f2d70dfb23f5b24477d3cc4fa471ea) 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.

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

The code fetches and potentially exposes sensitive authorization information in an insecure manner from Pastebin, which is a red flag for data security and integrity.

Malicious code in typeahead-client-logger (npm) Source: ghsa-malware (9121846b93247c8f8db2f98b553de9231e63282325f9bbaff65e8b6916d2a6cf) 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.

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

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

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.

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

Malicious code in frogsui (npm) Source: ghsa-malware (9baef0dc09c1323da3d13f47bc554883c6d7d3cee1c9afe05b9dbe94615b3939) 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.

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

Malicious code in @w3-commons/js-build-resources (npm) Source: ghsa-malware (7872915f84a85c03dfe50e7b7cef0787845ceaad3aac20ea1c20b7a844eb01e1) 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 seems to be suspicious as it reads system information and sends it to a remote server without a clear purpose. The presence of a hardcoded remote server address and the lack of user consent raise concerns about the intent of the code. Additionally, the 'debugger' keyword suggests that the code may have been used for debugging purposes and should not be present in production code.

The code snippet is highly obfuscated, making it difficult to ascertain its true intent or potential security risks. Without proper documentation or context, it is challenging to determine if there are any malicious behaviors present. Therefore, the security risk and malware likelihood cannot be definitively assessed.

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

Malicious code in curri-slack (npm) Source: ghsa-malware (a00fcf2aed2ef83f63aa909e95ceaeba67a19ae3189fe65bda5debdb8856e229) 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.

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

The code is highly suspicious and potentially malicious. It collects system information and sends it to a third-party site via DNS requests, which could be used for data exfiltration or tracking. It is recommended to avoid using this package due to the high security risk it poses.

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

Malicious code in azure-template-samples-ts-beta (npm) Source: ghsa-malware (b10d6fbf59581245f9918f3edb36dbc7879dee46d5b4d15555e411f29da0cf76) 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.

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

Malicious code in usaa-typography (npm) Source: ghsa-malware (5c459f6f99ba8293610148243ff44fd4b6810f70dcb75441158c134021cb7e95) 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.

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

Malicious code in brave-core-crx-packager (npm) Source: ghsa-malware (9d659bff6641ae2eba134b7096de9c5134287f99bb6aad5396c9f30be533d099) 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.

Malicious code in azure-arm-postgresql-flexible-samples-js (npm) Source: ghsa-malware (c67780d0043880a352f0f1137b729e497fa946b957fae4ca0f72384df954fa8e) 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.

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

The code poses a significant privacy risk as it captures and sends desktop screenshots without explicit user consent. The destination of the data is unknown, raising concerns about potential data theft or unauthorized surveillance.

Malicious code in body-complex (npm) Source: ghsa-malware (ef48c53ad39055a3692dbe528815988861df665507cc31c52dad47e5f746b3e3) 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.

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

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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