News, news analysis, and commentary on the latest trends in cybersecurity technology.
Checkmarx Launches Threat Intelligence for Open Source Packages
The new API incorporates threat intelligence research and employs machine learning to identify threats in the supply chain.
Software supply chain attacks where attack groups are tricking software developers into integrating malicious open source components into their applications are on the rise. To help developers identify malicious packages, Checkmarx has launched Supply Chain Threat Intelligence, an API that delivers detailed threat intelligence on hundreds of thousands of malicious packages, contributor reputation, and malicious behavior.
Checkmarx says it identifies malicious packages by attack type, such as dependency confusion, typosquatting, and chainjacking. And contributor reputation is calculated by analyzing anomalous activity within packages.
Supply Chain Threat Intelligence is based on threat intelligence research by Checkmarx Labs and includes the 150,878 malicious packages the group discovered in 2022, the company says. Checkmarx then employs machine learning, retro-hunting, and cross-language hunting to identify emerging threats. The company also uses static and dynamic analysis to understand how the code in the package runs.
Security works best when it is part of the developer workflow. Checkmarx says Supply Chain Threat Intelligence integrates with widely used developer tools and environments. The developer obtains a unique token from Checkmarx, sends in a package name and its version number, and receives threat intelligence on the desired package. The developer then has information on what the package does, whether the package is considered malicious, and the reputation of the developer associated with the package.
Reporting packages don't stop attack groups, as they create new sock-puppet accounts and continue publishing them, Checkmarx says. The company maintains a data lake of all the packages scanned so that the team can continue analyzing them even after they have been deleted from package managers, the company says. This can help link multiple packages to the same threat actor or uncover patterns over time.
About the Author
You May Also Like
Securing Tomorrow, Today: How to Navigate Zero Trust
Nov 13, 2024The State of Attack Surface Management (ASM), Featuring Forrester
Nov 15, 2024Applying the Principle of Least Privilege to the Cloud
Nov 18, 2024The Right Way to Use Artificial Intelligence and Machine Learning in Incident Response
Nov 20, 2024Safeguarding GitHub Data to Fuel Web Innovation
Nov 21, 2024