Package evidence

@inetafrica/[email protected]

Remote Payload: 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: 3,154Niche · −30% score
Versions published: 130
First published: Apr 2026
Publisher: inetafrica

Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Review before promoting

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

Inspect tarball Add 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":["@inetafrica/[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":["@inetafrica/[email protected]"],"fail_on":"review"}'

Publisherinetafrica

Artifact bytes217,219

Previous version2.6.7

Published2026-06-13T13:05:26.158Z

SHA-256d43ff65cc46c93ccc35054998f39c588ed1b011e2a77a9e2e233d0612a05888e

Why flagged

What the scanner saw

Remote Payload: matched "api.telegram.org/bot"

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

Availability ledger

available

review

2h agoLast checked

reviewRisk

39Score

2.6.8Version

Status history (1 event)

new → available2h ago · risk review · score 39 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
medium	Remote Payload	package/health.js	matched "api.telegram.org/bot"	12
medium	Remote Payload	package/setup.js	matched "api.telegram.org/bot"	12
medium	Remote Payload	package/web.js	matched "api.telegram.org/bot"	12

Show all 7 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
medium	Remote Payload	package/health.js	matched "api.telegram.org/bot"	12
medium	Remote Payload	package/setup.js	matched "api.telegram.org/bot"	12
medium	Remote Payload	package/web.js	matched "api.telegram.org/bot"	12
low	Messenger Bot Endpoint	package/bot-agent.js	matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)	5
low	Messenger Bot Endpoint	package/health.js	matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)	5
low	Messenger Bot Endpoint	package/setup.js	matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)	5
low	Messenger Bot Endpoint	package/web.js	matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)	5

Manifest

Package metadata

Scripts3

setupnode setup.js
startnode bot.js
testnode -e "require('./vault'); console.log('OK')"

Dependencies3

node-cron^4.2.1
node-telegram-bot-api^0.67.0
socket.io-client^4.7.5