Add supply-chain exposure catalog https-socket-dev-blog-npm-rat-targets-alibaba - #72
Open
ronheichman wants to merge 1 commit into
Open
Conversation
…ts-alibaba Co-Authored-By: Claude Code <noreply@anthropic.com>
Contributor
Author
|
@thom-pplx requesting your review on this catalog. The reviewer field cannot be set from this account: the PR comes from a fork and ronheichman has pull-only access on this repo, so |
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
1 participant
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.
What
Adds one exposure catalog for the 2026-07-28 npm RAT cluster that targeted Alibaba developers: 17 packages, each matching every version because the advisory names none. Adds one row to the catalog index.
Why
This campaign had no catalog here. npm replaced the packages with holding placeholders, so a scan cannot find them by asking the registry, yet any endpoint that installed one still carries it.
Each package cleared two independent checks before it entered the file: an OSV malicious-code record, and npm removal.
How we verified it
Built this repo's scanner from
d76e369, loaded the whole catalog directory, and scanned a tree holdinglib-mtopat an arbitrary version. It reported a critical finding, evidenceexact name match, catalog entry matches any version.Note:
schema_versionis 0.2.0, so this needs the any-version support from #65. The newest tag accepts 0.1.0 only.Built with Claude Code.