PkgRadar

npm · registry.npmjs.org

@fvckerss/baileys

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

Why PkgRadar flagged 1.0.2

SeveritySignalEvidence
highNew Account With Lifecycle Hookpackage first published 0 day(s) ago, 3 total version(s), has lifecycle hook · package.json
mediumRemote Payloadmatched "raw.githubusercontent.com" · package/lib/Utils/generics.js
mediumRemote Dependency Specdependencies.libsignal="git+https://github.com/whiskeysockets/libsignal-node" · package.json
mediumSuspicious Publish Context{"package_age_days":0,"publisher":"swipergod","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

Scanned versions

VersionVerdictScoreScanned (UTC)
1.0.2High risk392026-06-18
1.0.1High risk392026-06-18
1.0.0High risk392026-06-18

Block this in CI

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

pkgradar gate --ecosystem npm @fvckerss/[email protected]
@fvckerss/baileys — npm security scan | PkgRadar