@myorder-frontend-commons/analytics@3.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 install hooks activate a host-identification beacon that discloses identifying data to external, publisher-selected collectors without installer consent. This is malicious install-hook behavior under the installation beacon policy.
Decision evidence
public snapshot- package.json runs poc.js from preinstall, install, and postinstall hooks.
- poc.js defaults to two external collector hosts, with environment variables allowing destination overrides.
- The beacon payload includes package and lifecycle details, hostname, username, platform, working directory, Node version, and names of present CI variables.
- poc.js encodes the collected information into an HTTP request and sends it to both collectors when the script runs.
- The package describes itself as authorized security research, but that claim does not establish consent from the installing consumer.
Source & flagged code
9 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@3.0.0.
See all versions of @myorder-frontend-commons/analytics for other recorded verdicts.
- Avoid installing @myorder-frontend-commons/analytics@3.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.