Thursday, March 6, 2025
HomeCyber Security NewsPackage Analysis - OpenSSf Tool to Detect Malicious Packages in Popular Open-Source...

Package Analysis – OpenSSf Tool to Detect Malicious Packages in Popular Open-Source Repositories

Published on

SIEM as a Service

Follow Us on Google News

A prototype version of the Package Analysis tool has been recently released by the Open Source Security Foundation (OpenSSF), and it is the first of its kind to be published.

Using this tool, you can identify malicious attacks against open source registries in real-time and counter them. A short period of time after its release on GitHub, this tool identified more than 200 malicious packages using npm and PyPI in a pilot run that lasted less than a month.

This project analyses the packages found in open source repositories to find out:- 

  • How do they behave? 
  • What capabilities do they have?
  • What files do they access?
  • What addresses do they connect to?
  • What commands do they run?

Robust Tool to Scan open-source Repositories

This repository houses tools which are used to analyze open-source software packages, in particular, malware in the following packages:- 

  • npm packages
  • PyPI packages

As a result of this effort, open-source software will be better protected through the following reporting:-

  • Detecting malicious behavior.
  • Informing consumers selecting packages.
  • Providing researchers with data about the ecosystem.

There is one malicious package that has been identified by Package Analysis among all the suspect packages: ‘colorsss’. While this package has been found to be formerly deemed malicious.

Almost all of the packages that have been found contain a simple script that runs and requests a few details about the host from home during an installation process.

In most cases, these packages are created by security researchers looking to find bug bounties as part of a bug bounty program.

There is no attempt to conceal their behavior, and the majority of them are capable of extracting meaningful information from the system like:-

  • Name of the machine/system
  • Username

Future Goals

Here below we have mentioned all the future goals of the Package Analysis tool:-

  • The ability to detect changes in package behavior over time.
  • The packaging analysis results can be processed automatically after they have been received.
  • In order to maintain long-term analysis of the stored packages, they are stored themselves as they are processed.
  • The pipeline will gain greater reliability by improving its efficiency of the pipeline.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Implementing Identity First Security for Zero Trust Architectures

Zero Trust is a security framework that operates under the assumption that no implicit...

InvokeADCheck – New Powershell Module for Active Directory Assessment

Orange Cyberdefense has announced the development of InvokeADCheck, a new PowerShell module designed to...

Detecting Malicious Activities With Traffic Distribution Systems

Traffic Distribution Systems (TDS) have emerged as critical tools for both legitimate and malicious...

Hackers Deploy Advanced Social Engineering Tactics in Phishing Attacks

Cybercriminals are evolving their phishing methods, employing more sophisticated social engineering tactics to deceive...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Implementing Identity First Security for Zero Trust Architectures

Zero Trust is a security framework that operates under the assumption that no implicit...

InvokeADCheck – New Powershell Module for Active Directory Assessment

Orange Cyberdefense has announced the development of InvokeADCheck, a new PowerShell module designed to...

Detecting Malicious Activities With Traffic Distribution Systems

Traffic Distribution Systems (TDS) have emerged as critical tools for both legitimate and malicious...