htps-provider
This report shows the evidence for htps-provider@1.0.11. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-15567 confirms this npm version as malicious.
Advisory
MAL-2026-15567
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in htps-provider (npm)
Details
Package is published as htps-provider with a README copy-pasted verbatim from the legitimate Cosmos chain-registry project (advertising assets, chains, ibc exports and the same install/example snippets). The actual entrypoints do not expose that API: index.js and esm/index.mjs simply re-export HttpProvider from a runtime dependency named supersignaturenature (declared in package.json as "supersignaturenature": "^1.0.6"). esm/index.mjs performs a top-level static import of that dependency, so any ESM consumer that imports htps-provider immediately executes code from supersignaturenature. The name-and-README cover story, mismatched published API, and use of an obscurely-named third-party dependency as the sole runtime payload match the loader/stager half of a supply-chain attack, with the executable payload delivered through the transitively-installed dependency rather than this tarball. The chain.js files flagged by network/command patterns appear to be inert data/persistence modules unrelated to the loader path.
## Source: ghsa-malware (da0b78b1d8ceaa47ee7cfa5730bab8c05cfa585051fe78dee9464cad9f5f7588) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
Source inspection found no direct malicious action in this archive, but both public entry points delegate execution to an unrelated dependency and do not match the stated package role. Treat it as a staged payload carrier rather than a clean chain-registry package.
Static reason
No blocking static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer imports the ESM entry point or invokes HttpProvider through the CommonJS entry point.
Impact
The dependency receives execution in the consumer process, creating a staged dependency risk.
Mechanism
Third-party provider loading and re-exporting.
AI rationale
Source inspection found no direct malicious action in this archive, but both public entry points delegate execution to an unrelated dependency and do not match the stated package role. Treat it as a staged payload carrier rather than a clean chain-registry package.
Evidence
package.jsonindex.jsesm/index.mjstestnet/agoricdevnet/asset-list.js
Independent scan evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
- The package's CommonJS entry point dynamically imports and exposes code from supersignaturenature.
- The ESM entry point imports and re-exports the same third-party HttpProvider on package import.
- The manifest describes a chain registry but publishes provider-loader entry points, an inconsistent and suspicious package role.
Evidence against
- There are no preinstall, install, or postinstall lifecycle hooks.
- Inspected entry points contain no file harvesting, shell execution, credential access, or direct network request.
- The flagged asset-list file is static chain metadata, not executable attack logic.
Behavioral surface
HighEntropyStringsUrlStrings
Source & flagged code
2 flagged · loading sourcetestnet/agoricdevnet/asset-list.jsView file
•matchType = malicious_source_fingerprint_signature
signature = 96ca782747d1ea86
signatureType = suspicious_hashes
sourceLabel = OpenSSF malicious-packages
matchedPackage = mc-reg@1.0.4
matchedPath = testnet/agoricdevnet/asset-list.js
matchedIdentity = npm:bWMtcmVn:1.0.4
similarity = 1.000
shingleOverlap = 73
summary = Malicious code in mc-reg (npm)
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
testnet/agoricdevnet/asset-list.jsView on unpkgpackage.jsonView file
4"description": "Theta chain registry ⚛️",
"homepage": "https://github.com/hyperweb-io/htps-[redacted]-provider#readme",
"license": "MIT",
"main": "index.js",
"module": "esm/index.mjs",
High
Ai Review Evidence
The manifest describes a chain registry but publishes provider-loader entry points, an inconsistent and suspicious package role.
package.jsonView on unpkg · L4Findings
2 High3 Low
HighKnown Malware Source Fingerprint Signaturetestnet/agoricdevnet/asset-list.js
HighAi Review Evidencepackage.json
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to htps-provider@1.0.11.
The versions list below shows the verdict for each recorded version.
- Avoid installing htps-provider@1.0.11. 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.