dransay
This report shows the evidence for dransay@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.
OpenSSF/OSV Malicious Advisory
imported 11d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17700 confirms this npm version as malicious.
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
The install-time network beacon is limited to a fixed package label sent to an endpoint consistent with checking package resolution. The inspected source shows no concrete harmful behavior.
Independent scan evidence
public snapshot- package.json runs beacon.js during preinstall.
- beacon.js sends a DNS lookup and HTTPS GET containing only the fixed package label to an OAST host; no credential, file, or system-data collection is present in the inspected code.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
beacon.jsView on unpkgFindings
Affected versions and remediation
This report applies to dransay@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing dransay@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.