notify-utilities
Chain Dom
This report shows the evidence for notify-utilities@1.3.5, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe inspected source establishes an active, user-triggered remote payload execution chain. No lifecycle hook is needed for this to be malicious because ordinary use triggers arbitrary code fetched from a remote endpoint.
Decision evidence
public snapshot- `index.js` invokes detached `node lib/vcall.js` whenever its export is called.
- `lib/vcall.js` fetches a `model` field from `https://api.jsonsilo.com/public/df71fd55-4f0c-4326-9b5b-a285e38023a5`.
- `lib/vcall.js` compiles fetched content using `new Function.constructor` and executes it with `require`.
- `.env` contains redacted development credential keys, adding supply-chain hygiene concern.
- `package.json` contains no `preinstall`, `install`, or `postinstall` hook.
- Reviewed trigger path shows no direct local credential reading, file writes, or destructive action before remote code runs.
Source & flagged code
3 flagged · loading sourceSource fingerprint signature matches a known malicious package signature; route for source-aware review.
index.jsView on unpkgFindings
Affected versions and remediation
This report applies to notify-utilities@1.3.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing notify-utilities@1.3.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.