Package evidence
@bgx4k3p/[email protected]
Native Addon Gyp Action: binding.gyp runs a script or chains shell during node-gyp build (executes outside package.json lifecycle)
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
- 868
- Versions published
- 16
- First published
- Mar 2026
- Publisher
- bgx4k3p
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":["@bgx4k3p/[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":["@bgx4k3p/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 2.2.4 vs 2.2.3: "node scripts/patch-sdk.mjs"
1 candidate cluster(s) currently reference this release.
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 80 · status available -> available, risk high -> high, score 45 -> 80
- available → available · risk high · score 45 · status available -> available, risk high -> high, score 169 -> 45
- available → available · risk high · score 169 · status available -> available, risk high -> high, score 181 -> 169
- available → available · risk high · score 181 · status available -> available, risk high -> high, score 667 -> 181
- new → available · risk high · score 667 · status changed
Related candidates
Linked campaigns and clusters
Native Addon Gyp Action — binding.gyp runs a script or chains shell during node-gyp build (executes outside package.json lifecycle)
44 members · evidence strength 90Install-time lifecycle script — postinstall="node scripts/patch-sdk.mjs"
2 members · evidence strength 70Native Addon Gyp Action — binding.gyp runs a script or chains shell during node-gyp build (executes outside package.json lifecycle)
44 members · max score 147Evidence
Static findings
2 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 2.2.4 vs 2.2.3: "node scripts/patch-sdk.mjs" | 40 |
| high | Native Addon Gyp Action | package/node_modules/msgpackr-extract/binding.gyp | binding.gyp runs a script or chains shell during node-gyp build (executes outside package.json lifecycle) | 35 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 2.2.4 vs 2.2.3: "node scripts/patch-sdk.mjs" | 40 |
| high | Native Addon Gyp Action | package/node_modules/msgpackr-extract/binding.gyp | binding.gyp runs a script or chains shell during node-gyp build (executes outside package.json lifecycle) | 35 |
| low | Install-time lifecycle script | package.json | postinstall="node scripts/patch-sdk.mjs" | 5 |
Manifest
Package metadata
Scripts10
linteslint src/ scripts/packnode scripts/pack.mjspostinstallnode scripts/patch-sdk.mjsstartnode src/index.mjsstart:mcpnode src/mcp.mjsstart:servernode src/server.mjstestHULY_TRANSPORT=ws node --test test/integration.test.mjs && HULY_TRANSPORT=rest node --test test/integration.test.mjstest:restHULY_TRANSPORT=rest node --test test/integration.test.mjstest:wsHULY_TRANSPORT=ws node --test test/integration.test.mjsversion:syncnode -e "const{readFileSync:r,writeFileSync:w}=require('fs');const v=r('VERSION','utf-8').trim();const f='package.json';const j=JSON.parse(r(f,'utf-8'));j.version=v;w(f,JSON.stringify(j,null,2)+'\n');console.log('Synced version '+v+' to package.json')"
Dependencies2
@modelcontextprotocol/sdk^1.27.1jsdom^29.0.0