@johpaz/hive-agents

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: johpaz.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/cli/src/commands/gateway.ts#L382 380 | detached: true, 381 | stdio: ["ignore", openSync(logFile, "a"), openSync(logFile, "a")], > 382 | env: { ...process.env, HIVE_GATEWAY_CHILD: "1" }, 383 | }); 384 | child.unref();

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/cli/src/commands/gateway.ts#L492 490 | detached: true, 491 | stdio: ["ignore", "pipe", "pipe"], > 492 | env: { ...process.env, HIVE_DEV: "true", HIVE_GATEWAY_CHILD: "1" }, 493 | }); 494 |

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/cli/src/commands/gateway.ts#L665 663 | detached: true, 664 | stdio: ["ignore", "pipe", "pipe"], > 665 | env: { ...process.env, HIVE_GATEWAY_CHILD: "1", NO_BROWSER: "1", ...(getDistDir() ? { HIVE_DIST_DIR: getDistDir()! 666 | }); 667 |

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/cli/src/commands/mcp.ts#L125 123 | 124 | const proc = spawn(server.command, server.args || [], { > 125 | env: { ...process.env, ...server.env }, 126 | stdio: ["pipe", "pipe", "pipe"], 127 | });

URL pointing to known exfiltration/tunneling service Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/cli/src/commands/onboard.ts#L251 249 | try { 250 | const res = await fetch( > 251 | `https://api.telegram.org/bot${token}/getMe`, 252 | { signal: AbortSignal.timeout(5000) } 253 | );

URL pointing to known exfiltration/tunneling service Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/core/src/channels/telegram.ts#L178 176 | if (file.file_path) { 177 | image = { > 178 | url: `https://api.telegram.org/file/bot${this.config.botToken}/${file.file_path}`, 179 | mimeType: "image/jpeg", 180 | caption: caption || undefined,

URL pointing to known exfiltration/tunneling service Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/core/src/channels/telegram.ts#L201 199 | const filePath = file.file_path; 200 | if (filePath) { > 201 | audioUrl = `https://api.telegram.org/file/bot${this.config.botToken}/${filePath}`; 202 | } 203 | } catch (error) {

URL pointing to known exfiltration/tunneling service Source: https://github.com/johpaz/hive/blob/7ee98131f8c6edfcc8630416634e86687a372f69/packages/core/src/channels/telegram.ts#L249 247 | if (file.file_path) { 248 | document_ = { > 249 | url: `https://api.telegram.org/file/bot${this.config.botToken}/${file.file_path}`, 250 | mimeType: message.document.mime_type || "application/octet-stream", 251 | fileName: docName,

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.