Conversation
ericcornelissen
requested changes
Oct 2, 2026
ericcornelissen
left a comment
ericcornelissen
left a comment
Collaborator
There was a problem hiding this comment.
The proposal looks good but please resolve the CI failures.
|
We would like to do feedback on your paper if that is possible. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
SpiderScan: Practical Detection of Malicious NPM Packages Based on Graph-Based Behavior Modeling and Matching
Names and KTH ID
Deadline
Category
Description
Modern software development relies heavily on third-party packages and dependencies, making package ecosystems an attractive target for software supply chain attacks. Malicious packages can be difficult to detect because individual behaviors, such as accessing files or communicating over a network, can occur in both legitimate and malicious software.
The paper we have chosen to present, “SpiderScan: Practical Detection of Malicious NPM Packages Based on Graph-Based Behavior Modeling and Matching”, presents an approach for detecting malicious packages in the npm ecosystem. Instead of considering suspicious API calls only in isolation, SpiderScan models their relationships using behavior graphs that capture control flow and data dependencies. It then matches suspicious behavior against known malicious behavior patterns and uses additional verification to reduce false positives.
During the presentation we cover the problem of malicious packages, explain SpiderScan’s graph-based approach and evaluation. Discuss its DevSecOps and dependency-management implications, and critically compare its limitations with related approaches such as ProfMal and MalGuard.
Relevance
Third-party dependencies are an important part of modern DevOps pipelines, but they also introduce software supply chain security risks. Detecting malicious dependencies before they can compromise development, build, or deployment environments is therefore relevant to DevSecOps. SpiderScan addresses this problem by providing an automated approach for analyzing npm packages and identifying potentially malicious behavior.