@dransay/secrets
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/secrets@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 automatic preinstall hook performs an external beacon that reveals package resolution, and the source directly asserts its own benignness to the reviewer. The inspected behavior supports blocking as malicious; it does not show collection of local secrets or files.
Decision evidence
public snapshot- The preinstall hook automatically runs beacon.js during installation.
- The script sends a DNS lookup and HTTPS request containing the package name to an external OAST host.
- Source comments claim the beacon is benign and explicitly requested, directly asserting its own benignness to the reviewer.
- The request contains only the package name; the inspected code does not collect environment variables, files, or system information.
- The request has a timeout, and errors are ignored.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe preinstall hook automatically runs beacon.js during installation.
package.jsonView on unpkg · L10Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @dransay/secrets@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dransay/secrets@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.