@dransay/feature-flags
Benign dependency-confusion interaction beacon published at the explicit request of the DrAnsay/YesWeHack triage team (report #YWH-PGM42275-93). No data collection; see README.
This report shows the evidence for @dransay/feature-flags@99.0.0. 1 of 2 known versions is blocked or flagged. See all versions.
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 network beacon to a hard-coded external host, exposing installation activity and network source information without an evidenced user opt-in. This is concrete data disclosure, so blocking is warranted.
Decision evidence
public snapshot- The preinstall hook automatically runs the beacon during package installation.
- The beacon performs DNS and HTTPS requests to a hard-coded external host, with the package name in the request.
- The README describes the package as a benign security-research beacon, a claim that does not establish consent for the install-time callback.
- The inspected beacon sends a fixed package name and contains no visible environment or file collection.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe preinstall hook automatically runs the beacon during package installation.
package.jsonView on unpkg · L11Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @dransay/feature-flags@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dransay/feature-flags@99.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.