PkgRadar

npm · registry.npmjs.org

@polderlabs/bizarharness

New Account With Lifecycle Hook: package first published 0 day(s) ago, 5 total version(s), has lifecycle hook

Why PkgRadar flagged 2.1.6

SeveritySignalEvidence
highNew Account With Lifecycle Hookpackage first published 0 day(s) ago, 5 total version(s), has lifecycle hook · package.json
mediumRemote Payloadmatched "curl " · package/cli/copy.mjs
mediumRemote Payloadmatched "curl " · package/cli/install.mjs
mediumSuspicious Publish Context{"package_age_days":0,"publisher":"drb0rk","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":true}

Scanned versions

VersionVerdictScoreScanned (UTC)
2.1.6High risk392026-06-18
2.1.5High risk392026-06-18
2.1.4High risk392026-06-18
2.1.2High risk392026-06-18
2.1.3High risk392026-06-18

Block this in CI

PkgRadar gates @polderlabs/bizarharness (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm @polderlabs/[email protected]