@myorder-frontend-commons/analytics@5.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 11d ago · by lpm-firewall-aiThe package performs an automatic install-time disclosure of identifying host and CI data to publisher-selected external collectors without installer consent. This is a concrete installation beacon and warrants blocking.
Decision evidence
public snapshot- package.json runs poc.js automatically during preinstall, install, and postinstall.
- poc.js collects hostname, username, platform, working directory, Node version, package version, and present CI marker names.
- poc.js encodes the collected information into an outbound request path.
- poc.js sends the beacon to default external collectors without installer consent enforcement.
- The package describes the beacon as authorized research and says it avoids secret values, but those package-authored claims do not establish installer consent.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs poc.js automatically during preinstall, install, and postinstall.
package.jsonView on unpkg · L6Findings
Affected versions and remediation
This report applies to @myorder-frontend-commons/analytics@5.0.0.
See all versions of @myorder-frontend-commons/analytics for other recorded verdicts.
- Avoid installing @myorder-frontend-commons/analytics@5.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.