PkgRadar

Package evidence

@musistudio/[email protected]

Webhook Exfil Endpoint: matched "api.telegram.org/bot"

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Weekly downloads
134
Versions published
1
First published
Jun 2026
Publisher
musistudio

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["@musistudio/[email protected]"],"fail_on":"high"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["@musistudio/[email protected]"],"fail_on":"high"}'
Publishermusistudio
Artifact bytes98,098
Previous versionnone
Published2026-06-19T09:23:26.239Z
SHA-25639a8f8d802a9e321ca81b1bd2ec0d88f3820e490addb5946aef58ca0f9b11930

Why flagged

What the scanner saw

Webhook Exfil Endpoint: matched "api.telegram.org/bot"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

high
Last checked
highRisk
74Score
1.0.0Version
Status history (3 events)
  1. availableavailable · risk high · score 74 · status available -> available, risk high -> high, score 84 -> 74
  2. availableavailable · risk high · score 84 · status available -> available, risk high -> high, score 74 -> 84
  3. newavailable · risk high · score 74 · status changed

Evidence

Static findings

4 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highWebhook Exfil Endpointpackage/dist/src/channels/telegram/actions.jsmatched "api.telegram.org/bot"40
highWebhook Exfil Endpointpackage/dist/src/channels/telegram/polling-manager.jsmatched "api.telegram.org/bot"40
mediumRemote Payloadpackage/dist/src/channels/telegram/actions.jsmatched "api.telegram.org/bot"12
mediumRemote Payloadpackage/dist/src/channels/telegram/polling-manager.jsmatched "api.telegram.org/bot"12

Manifest

Package metadata

Scripts21
  • buildnpm run clean && tsc -p tsconfig.json
  • bundlenpm run clean:bundle && node scripts/bundle.mjs
  • bundle:servernode scripts/bundle.mjs server
  • bundle:stdionode scripts/bundle.mjs stdio
  • cleanrm -rf dist
  • clean:bundlerm -rf dist-bundle
  • devtsx watch src/server.ts
  • dev:stdiotsx src/stdio.ts
  • pack:dry-runnpm pack --dry-run
  • playground:replnpm --prefix sdks/node run build && node scripts/repl-playground.mjs
  • prepacknpm run build
  • prepublishOnlynpm test
  • release:checknpm test && npm run pack:dry-run
  • release:publishnpm publish --access public
  • release:publish:provenancenpm publish --access public --provenance
  • startnode dist/src/server.js
  • start:bundle:servernode dist-bundle/server/server.js
  • start:bundle:stdionode dist-bundle/stdio/stdio.js
  • start:stdionode dist/src/stdio.js
  • sync:sdk-stdionpm run bundle:stdio && node scripts/sync-sdk-stdio.mjs
  • testnode --test --import tsx tests/**/*.test.ts
Dependencies7
  • @fastify/websocket^11.2.0
  • @larksuiteoapi/node-sdk^1.63.0
  • fastify^5.3.0
  • https-proxy-agent^9.0.0
  • socks-proxy-agent^10.0.0
  • undici^7.25.0
  • ws^8.20.0