@myorder-frontend-commons/analytics@2.0.0
AUTHORIZED security research PoC (dependency-confusion test for Allegro, with written permission from Allegro Cybersecurity). Harmless: emits a single host-identification beacon on install to confirm code execution in the build/CI environment, then exits.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe lifecycle hooks activate an outbound disclosure of machine-identifying data to preset external collectors. This is concrete install-time data exfiltration.
Decision evidence
public snapshot- The package runs poc.js automatically during preinstall, install, and postinstall.
- The script collects the machine hostname, username, platform details, and working directory.
- It encodes collected information into an outbound request path.
- It sends the beacon to preset external collectors without a consent check.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs poc.js automatically during preinstall, install, and postinstall.
package.jsonView on unpkg · L5Findings
Affected versions and remediation
This report applies to @myorder-frontend-commons/analytics@2.0.0.
See all versions of @myorder-frontend-commons/analytics for other recorded verdicts.
- Avoid installing @myorder-frontend-commons/analytics@2.0.0. 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.