Installation metadata is disclosed to the reporting service without an affirmative installer choice.
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 install-time reporting is enabled for this package and sends environment and dependency metadata to an unrelated reporting service without affirmative installer consent. This supports blocking as install-hook disclosure.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing @aviaviavi/org2 with npm, which installs the declared @scarf/scarf dependency.
Mechanism
The dependency’s postinstall runs a reporter that defaults to opt-in and sends a POST containing platform, architecture, Node.js version, and dependency information.
Attack narrative
The package declares @scarf/scarf and enables its top-level reporting path. That dependency runs a postinstall reporter; reporting defaults to opt-in, and the active default path does not require an installer confirmation. The reporter sends installation and environment metadata to scarf.sh.
Avoid installing @aviaviavi/org2@0.8.6. 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.