Add OSV reports for click2ai dependency-confusion campaign (npm, 17 packages)#1348
Merged
elitsa-gosst merged 3 commits intoJul 13, 2026
Merged
Conversation
…ackages) npm user 'click2ai' (privatek3m@protonmail.com) published 14 brand-lookalike packages across multiple internal/private namespaces (@logdna-web, @flex-ng, @idms-corp, enbd-*, tme-*, box-*, sams-*). Each carries an identical preinstall beacon that runs at install time: it resolves the host's public IP via Cloudflare /cdn-cgi/trace and exfiltrates host PII to a hardcoded attacker Sentry DSN, with a distinct Sentry project ID per impersonated namespace. Signed-off-by: Kunal Singh <kunalsin9h@gmail.com>
Collaborator
|
There are 3 more packages that have been added in the last 3 days: https://www.npmjs.com/~click2ai |
elitsa-gosst
approved these changes
Jul 13, 2026
Signed-off-by: Kunal Singh <kunalsin9h@gmail.com>
Contributor
Author
|
Thanks @elitsa-gosst! Good catch — I've added the 3 additional packages from the same
Each carries the same install-time payload as the other 14 (identical |
elitsa-gosst
approved these changes
Jul 13, 2026
Collaborator
|
Thanks for updating with the rest of the packages! |
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
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.
Summary
Reports 17 malicious npm packages published by npm user
click2ai(maintainer emailprivatek3m@protonmail.com). The packages form a dependency-confusion / reconnaissance campaign: each uses a brand-lookalike name impersonating an organization's internal/private package namespace so a misconfigured resolver installs the public lookalike.Behavior (identical across all 17)
Each package declares a
preinstallhook:At install time, before any application code runs, the bundled
examples/verify.js→src/index.js:@sentry/nodeagainst a hardcoded, attacker-controlled Sentry DSN withsendDefaultPii: true./cdn-cgi/trace(spoofed desktop-browser User-Agent to bypass bot challenges).o4510485815754752.ingest.us.sentry.io.The install-time payload is byte-for-byte identical across all packages, differing only in package name and DSN. Each impersonated namespace beacons to a distinct Sentry project ID, letting the operator attribute installs to specific victim organizations — consistent with a dependency-confusion recon beacon, not legitimate error monitoring.
Packages (17)
@idms-corp/auth-ui@flex-ng/header-component@flex-ng/error-component@flex-ng/filter-pipe@logdna-web/styles@logdna-web/sharedtme-xcatme-xca-reacttme-errorenbd-react-loggerenbd-react-error-boundryenbd-react-libbox-react-uixsams-sr-sdk-h5chat-adapter-zoomsalesforce-vscode-sldsslds-lsp-client