PkgRadar

npm · registry.npmjs.org

@mirageshield/mirage

Install Lifecycle Remote Or Exec: postinstall="node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""

Why PkgRadar flagged 0.2.0

SeveritySignalEvidence
highInstall Lifecycle Remote Or Execpostinstall="node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\"" · package.json
highNew Account With Lifecycle Hookpackage first published 0 day(s) ago, 3 total version(s), has lifecycle hook · package.json
mediumSuspicious Publish Context{"package_age_days":0,"publisher":"magicmisty","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

Scanned versions

VersionVerdictScoreScanned (UTC)
0.2.0High risk452026-06-18
0.1.1Review102026-06-18
0.1.2High risk852026-06-18

Campaign attribution

Part of the Clob dropper campaign.

Related campaigns

Block this in CI

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

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