@myorder-frontend-commons/analytics@1.1.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 install hooks activate network disclosure of host and CI identifiers to default external collectors, establishing concrete installation-time data exfiltration. Claims of authorized research in package text do not establish installer consent.
Decision evidence
public snapshot- package.json runs poc.js from preinstall, install, and postinstall hooks.
- poc.js collects the machine hostname, username, platform, working directory, Node version, package version, and present CI variable names.
- poc.js encodes the collected values into an HTTP query string.
- poc.js selects researcher-controlled default collectors unless environment overrides are set.
- poc.js sends HTTP GET requests to the selected host on port 80.
- poc.js invokes the beacon for both the hostname-derived OOB host and the backup collector.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs poc.js from preinstall, install, and postinstall hooks.
package.jsonView on unpkg · L7Findings
Affected versions and remediation
This report applies to @myorder-frontend-commons/analytics@1.1.0.
See all versions of @myorder-frontend-commons/analytics for other recorded verdicts.
- Avoid installing @myorder-frontend-commons/analytics@1.1.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.