PkgRadar

Package evidence

[email protected]

Messenger Bot Endpoint: matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)

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
48
Versions published
3
First published
May 2026
Publisher
yiyao-ai

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarballAdd to CI gate
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":["[email protected]"],"fail_on":"review"}'

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":["[email protected]"],"fail_on":"review"}'
Publisheryiyao-ai
Artifact bytes13,550,151
Previous version1.2.3
Published2026-06-05T09:16:07.292Z
SHA-2560502f2419aace917e06ff184aed7891c9972b96216fca12981ff4fd38cbad81e

Why flagged

What the scanner saw

Messenger Bot Endpoint: matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)

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

Availability ledger

available

review
Last checked
reviewRisk
5Score
1.2.4Version
Status history (1 event)
  1. new → available · risk review · score 5 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowMessenger Bot Endpointpackage/src/agent-channels/providers/telegram-provider.jsmatched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)5

Manifest

Package metadata

Scripts28
  • accountsnode src/cli/accounts.js
  • accounts:addnode src/cli/accounts.js add
  • accounts:add:headlessnode src/cli/accounts.js add --no-browser
  • accounts:listnode src/cli/accounts.js list
  • accounts:removenode src/cli/accounts.js remove
  • accounts:verifynode src/cli/accounts.js verify
  • desktop:mvpnode scripts/desktop-agent/mvp-run.js
  • electronelectron .
  • electron:buildelectron-builder --win
  • electron:build:allelectron-builder --win --mac --linux
  • pack:dry-runnode scripts/release-check.js --pack-only
  • prepublishOnlynpm run release:check
  • release:checknode scripts/release-check.js
  • startnode src/index.js
  • testnode --test tests/*.test.js
  • test:allnode --test tests/unit/*.test.js tests/*.test.js
  • test:apinode --test tests/api.test.js
  • test:corsnode --test tests/cors_security.test.js
  • test:e2e:clinode tests/e2e/lib/cli-runner.js
  • test:e2e:cli:isolatednode tests/e2e/lib/run-isolated-cli.js
  • test:e2e:cli:listnode tests/e2e/lib/cli-runner.js --list
  • test:e2e:isolatednpm run test:e2e:protocol:isolated && npm run test:e2e:cli:isolated
  • test:e2e:protocolnode tests/e2e/lib/scenario-runner.js
  • test:e2e:protocol:isolatednode tests/e2e/lib/run-isolated-protocol.js
  • test:e2e:protocol:listnode tests/e2e/lib/scenario-runner.js --list
  • test:routingnode --test tests/routing.test.js
  • test:uinode --test tests/ui.test.js
  • test:unitnode --test tests/unit/*.test.js
Dependencies5
  • @larksuiteoapi/node-sdk^1.61.0
  • cors^2.8.5
  • express^4.18.2
  • fzstd^0.1.1
  • js-yaml^4.2.0