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.
- Versions published
- 139
- First published
- May 2026
- Publisher
- dasrebel
Recommended action
Block this updateStatic 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":["[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":["[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Credential File Packaged: package/.env
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (4 events)
- available → available · risk high · score 50 · status available -> available, risk high -> high, score 35 -> 50
- available → available · risk high · score 35 · status available -> available, risk high -> high, score 50 -> 35
- available → available · risk high · score 50 · status available -> available, risk high -> high, score 71 -> 50
- new → available · risk high · score 71 · status changed
Related candidates
Linked campaigns and clusters
dasrebel
15 members · evidence strength 78Evidence
Static findings
4 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential File Packaged | package/.env | package/.env | 35 |
Show all 4 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential File Packaged | package/.env | package/.env | 35 |
| low | Credential file access | package/dist/providers/providerConfig.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Messenger Bot Endpoint | package/dist/integrations/telegram.js | matched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler) | 5 |
| low | Credential file access | package/src/providers/providerConfig.ts | matched "AWS_ACCESS_KEY" | 5 |
Manifest
Package metadata
Scripts5
buildtscdemonode demo/research-demo.jsprepublishnpm run buildpython:examplespython3 python/examples.pytestnode test/verify.js
Dependencies1
nanoid^5.0.0