@securihackbot/depconf-flow-1792484611@1.2.1
Dependency-confusion research PoC (authorized). Non-executing placeholder by default.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest activates the hook during installation, and the source shows identifying environment data sent to an external package-selected endpoint by default. This is automatic installation-time disclosure without an affirmative consent gate, supporting a block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package runs its postinstall hook.
Impact
The callback can learn identifying details about the build host and package installation without an affirmative installer consent gate.
Mechanism
The hook collects host and user identifiers and runtime details, encodes them, and sends them in an HTTP or HTTPS request to a package-selected default endpoint; it also performs a nonce-based DNS lookup.
Attack narrative
During package installation, the postinstall hook collects host and user identifiers along with platform and runtime details. It sends the encoded data to a package-selected callback by default and makes a nonce-based DNS query, exposing installation environment information without an affirmative consent gate.
AI rationale
The manifest activates the hook during installation, and the source shows identifying environment data sent to an external package-selected endpoint by default. This is automatic installation-time disclosure without an affirmative consent gate, supporting a block.
Evidence
package.jsonpostinstall.js
Network endpoints2
34.143.131.27:18080/test-eng-VA-999/main.abc123.jsYOUR-COLLABORATOR.example
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package manifest runs postinstall.js automatically during installation.
- The install script defines a package-selected callback URL by default.
- The script collects the package name, host name, user name, platform, architecture, and runtime version.
- The script encodes the collected data into a request parameter and sends an HTTP or HTTPS GET.
- The script also performs a DNS lookup using the nonce and configured suffix.
Evidence against
Behavioral surface
EnvironmentVarsNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node postinstall.js"
},
"files": [
"index.js",
"post
High
Suspicious Lifecycle Evidence
The package manifest runs postinstall.js automatically during installation.
package.jsonView on unpkg · L7•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpostinstall.jsView file
Findings
2 Critical3 High4 Medium3 Low
CriticalHardcoded Runtime Data Exfiltrationpostinstall.js
CriticalTrigger Reachable Dangerous Capabilitypostinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @securihackbot/depconf-flow-1792484611@1.2.1.
See all versions of @securihackbot/depconf-flow-1792484611 for other recorded verdicts.
- Avoid installing @securihackbot/depconf-flow-1792484611@1.2.1. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.