Installation metadata is disclosed to a third-party collector without installer consent.
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
Source inspection confirms an automatic postinstall disclosure to scarf.sh that is enabled by default for this package. The reporter offers an opt-out, but no affirmative consent is required before the installation event is sent.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An npm installation that runs the @scarf/scarf postinstall hook, unless analytics has been disabled.
Mechanism
The package enables top-level reporting; the dependency's default-enabled path sends an HTTPS install event with environment and dependency metadata to scarf.sh without requiring affirmative opt-in.
Attack narrative
The package includes @scarf/scarf and enables its top-level reporting. The dependency runs report.js from postinstall; its default-enabled path proceeds unless an opt-out is present, then sends installation metadata to scarf.sh. This is automatic installation-time disclosure without affirmative installer consent. The inspected payload construction covers platform, architecture, Node version, and dependency information; it does not establish credential theft.
Avoid installing @aviaviavi/org2@0.8.4. 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.