Analyzing Supply Chain Malware Artifacts
Structure supply-chain malware sample analysis into a severity-ranked report with IOCs and actionable recommendations.
Overview
Analyzing-supply-chain-malware-artifacts is an agent skill for the Ship phase that structures supply-chain malware sample analysis into findings, IOCs, and recommendations using a fixed report template.
Install
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill analyzing-supply-chain-malware-artifactsWhat is this skill?
- Standard analysis report table for sample SHA-256, type, date, analyst, and TLP:AMBER classification
- Findings grid with severity and details per row
- Dedicated IOC extraction table (type, value, context)
- Numbered recommendations section for remediation follow-up
- Template-oriented workflow for consistent supply-chain malware write-ups
- Report template includes 3 numbered recommendation slots
- Structured tables for sample info, findings, and IOCs
Adoption & trust: 1 installs on skills.sh; 14.9k GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have a suspicious supply-chain sample but no consistent format to capture severity, IOCs, and next steps for stakeholders.
Who is it for?
Builders or analysts documenting malware-linked dependency artifacts after initial collection of hash and file type.
Skip if: Routine npm/pip version bumps with no malicious indicators, or fully automated pipeline triage with no human report step.
When should I use this skill?
User needs to analyze or document supply-chain malware artifacts, IOCs, and severity-ranked findings from a collected sample.
What do I get? / Deliverables
You produce a TLP-aware analysis report with tabular findings, extracted IOCs, and ordered recommendations ready to share with your team.
- Completed analysis report with sample metadata table
- Findings table with severity columns
- IOC list and numbered recommendations
Recommended Skills
Journey fit
Malware artifact analysis fits pre-release and dependency-trust review—security hardening before you ship or promote packages. Supply-chain malware triage is app security work: classifying samples, extracting IOCs, and documenting findings before production trust.
How it compares
Use this documentation template instead of free-form chat summaries when you need audit-ready supply-chain malware notes.
Common Questions / FAQ
Who is analyzing-supply-chain-malware-artifacts for?
Solo builders, indie SaaS founders, and small teams who investigate compromised packages or artifacts and must report IOCs clearly.
When should I use analyzing-supply-chain-malware-artifacts?
During Ship security when you are analyzing supply-chain malware artifacts and need structured findings, IOC tables, and recommendations before trusting a release.
Is analyzing-supply-chain-malware-artifacts safe to install?
Check the Security Audits panel on this Prism page; handling real malware samples should stay in isolated analysis environments regardless of skill content.
SKILL.md
READMESKILL.md - Analyzing Supply Chain Malware Artifacts
# Analysis Report Template - analyzing-supply-chain-malware-artifacts ## Sample Information | Field | Value | |-------|-------| | SHA-256 | | | File Type | | | Analysis Date | | | Analyst | | | Classification | TLP:AMBER | ## Findings | Finding | Severity | Details | |---------|----------|---------| | | | | ## IOCs Extracted | Type | Value | Context | |------|-------|---------| | | | | ## Recommendations 1. 2. 3. Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditi