Installation details leave the consumer environment automatically.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The dependency's reachable postinstall sends installation metadata to a publisher-selected external collector without requiring affirmative installer consent. This concrete installation beacon warrants blocking under the install-hook policy.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing @aviaviavi/org2 with dependency lifecycle scripts enabled.
Mechanism
The @scarf/scarf postinstall runs a reporter that sends platform, architecture, Node version, and dependency information to scarf.sh unless the installer has opted out.
Attack narrative
The package declares @scarf/scarf as a dependency and enables its top-level reporting setting. That dependency has a postinstall hook which runs its reporter. The reporter defaults to opt-in behavior and sends installation metadata, including platform and dependency information, to scarf.sh unless the installer has opted out. This is an automatic installation disclosure, not evidence of secret collection.
Avoid installing @aviaviavi/org2@0.7.2. 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.