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
- 186
- Versions published
- 64
- First published
- Feb 2026
- Publisher
- prooflayer
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
Webhook Exfil Endpoint: matched "webhook.site"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (5 events)
- available → available · risk high · score 75 · status available -> available, risk high -> high, score 267 -> 75
- available → available · risk high · score 267 · status available -> available, risk high -> high, score 222 -> 267
- available → available · risk high · score 222 · status available -> available, risk high -> high, score 247 -> 222
- available → available · risk high · score 247 · status available -> available, risk high -> high, score 1299 -> 247
- new → available · risk high · score 1299 · status changed
Related candidates
Linked campaigns and clusters
Install-time lifecycle script — postinstall="node scripts/postinstall.js"
158 members · evidence strength 90Credential file access — matched "aws_secret_access_key"
11 members · evidence strength 90prooflayer
2 members · evidence strength 64Evidence
Static findings
10 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Webhook Exfil Endpoint | package/src/tools/scan-action.js | matched "webhook.site" | 40 |
Show all 10 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Webhook Exfil Endpoint | package/src/tools/scan-action.js | matched "webhook.site" | 40 |
| low | Credential file access | package/src/fix-patterns.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/src/tools/scan-skill.js | matched ".npmrc" | 5 |
| low | Credential file access | package/regex_fallback.py | matched "aws_secret_access_key" | 5 |
| low | Install-time lifecycle script | package.json | postinstall="node scripts/postinstall.js" | 5 |
| low | Credential file access | package/rules/agent-attacks.security.yaml | matched "id_rsa" | 3 |
| low | Credential file access | package/rules/generic.secrets.yaml | matched "aws_secret_access_key" | 3 |
| low | Credential file access | package/rules/python/boto3/security/hardcoded-token.yaml | matched "aws_access_key" | 3 |
| low | Credential file access | package/rules/third-party/shopify/python/boto3/security/hardcoded-token.yaml | matched "aws_secret_access_key" | 3 |
| low | Credential file access | package/rules/openclaw.security.yaml | matched "id_rsa" | 3 |
Manifest
Package metadata
Scripts6
benchmarkpython3 benchmarks/benchmark_runner.py --save --compare-latestpostinstallnode scripts/postinstall.jsstartnode index.jstestvitest runtest:coveragevitest run --coveragetest:watchvitest
Dependencies4
@modelcontextprotocol/sdk^1.25.3bloom-filters^3.0.4tar^7.5.9zod^4.3.6