@conduitops/logview-archive@1.0.1
Streaming authenticated encryption, key management and log-archive formats for retained logs
AI Security Review
scanned 15h ago · by lpm-firewall-aiThe automatic postinstall fetches a separate package from an obfuscated, non-HTTPS registry, and the source explicitly describes the masking as defeating string scans. This concealed install-time remote package chain supports blocking publication.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing this package with lifecycle scripts enabled runs its postinstall hook.
Impact
The install contacts the concealed registry and permits npm to process a remote package and its lifecycle behavior during installation.
Mechanism
The hook decodes a registry address and invokes npm to install @conduit/logview-cli@2.2.0 into a vendor directory.
Attack narrative
During postinstall, the package decodes an obfuscated registry address and invokes npm to install a pinned CLI package from that HTTP endpoint. The decoder source says the masking defeats string scans. This creates a concealed remote package installation chain during consumer installation.
AI rationale
The automatic postinstall fetches a separate package from an obfuscated, non-HTTPS registry, and the source explicitly describes the masking as defeating string scans. This concealed install-time remote package chain supports blocking publication.
Evidence
package.jsoninstall.jslib/toolchain.jsonlib/origin.js
Network endpoints1
139.196.94.195:8080/dl/npm/
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package manifest runs install.js automatically during postinstall.
- The hook installs a separate CLI package into a vendor directory and supplies a decoded registry address to npm.
- The registry address is XOR/base64 encoded and decodes to an HTTP endpoint at 139.196.94.195:8080.
- The decoder’s source explains that masking defeats string scans.
Evidence against
- The install targets a package-local vendor directory and skips installation when the host already provides the CLI.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStrings
NoLicense
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg13"postinstall": "node install.js"
},
"files": [
"index.js",
"install.js",
"lib/",
"src/",
"bin/",
"types/",
"README.md"
],
"engines": {
"node
High
Suspicious Lifecycle Evidence
The package manifest runs install.js automatically during postinstall.
package.jsonView on unpkg · L13•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgsrc/core/bytes.js#virtual:normalized:round1View file
Findings
5 High3 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedsrc/core/bytes.js#virtual:normalized:round1
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidenceinstall.js
HighAi Review Evidenceinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowNo License
Affected versions and remediation
This report applies to @conduitops/logview-archive@1.0.1.
See all versions of @conduitops/logview-archive for other recorded verdicts.
- Avoid installing @conduitops/logview-archive@1.0.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.