@dransay/api
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/api@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 10d ago · by lpm-firewall-aiThe package has an active preinstall disclosure to a publisher-selected research/OOB collector without installer consent, which meets the installation beacon blocking policy. The source’s claims of benignness and a triage-team request do not establish consent.
Decision evidence
public snapshot- `package.json` runs `node beacon.js` automatically during preinstall.
- `beacon.js` sends the package name in a DNS lookup and HTTPS GET to an OAST collector; the installer is given no consent guard.
- A source comment asserts the beacon is benign and was requested by a triage team; that claim does not establish installer consent.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkg`package.json` runs `node beacon.js` automatically during preinstall.
package.jsonView on unpkg · L11Source fingerprint signature matches a known malicious package signature; route for source-aware review.
beacon.jsFindings
Affected versions and remediation
This report applies to @dransay/api@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dransay/api@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.