Skip to main content
Scans/npm/drizzy-agent

drizzy-agent

npm

Share

Summary

drizzy-agent v0.7.1 was classified as CRITICAL RISK with a risk score of 1130. Sigil detected 71 findings across 1020 files, covering phases including install hooks, code patterns, obfuscation. Review the findings below before installing this package.

CRITICAL RISK(1130)

v0.7.1

23 March 2026, 06:48 UTC

by Sigil Bot

Risk Score

1130

Findings

71

Files Scanned

1020

Provenance

Findings by Phase

Phase Ordering

Phases are ordered by criticality, with the most dangerous at the top. Click any phase header to expand or collapse its findings. Critical phases are expanded by default.

install-makefile-curl

HIGH

Makefile/script pipes remote content to shell

package/dist/cli/index.js:4215

      success: false,
      error: `bun install failed: ${message}. Is bun installed? Try: curl -fsSL https://bun.sh/install | bash`
    };
Why was this flagged?

A script or Makefile pipes content from a remote URL directly into a shell (curl | sh or wget | bash). This is inherently dangerous because the remote content can change at any time, and the command runs with the current user's permissions. Rated HIGH because it requires manual execution (unlike install hooks) but still executes arbitrary remote code.

install-makefile-curl

HIGH

Makefile/script pipes remote content to shell

package/dist/index.js:40485

      success: false,
      error: `bun install failed: ${message}. Is bun installed? Try: curl -fsSL https://bun.sh/install | bash`
    };
Why was this flagged?

A script or Makefile pipes content from a remote URL directly into a shell (curl | sh or wget | bash). This is inherently dangerous because the remote content can change at any time, and the command runs with the current user's permissions. Rated HIGH because it requires manual execution (unlike install hooks) but still executes arbitrary remote code.

install-npm-postinstall

CRITICAL

npm lifecycle script — runs automatically on install

package/package.json:30

    "prepare": "bun run build",
    "postinstall": "node postinstall.mjs",
    "prepublishOnly": "bun run clean && bun run build",
Why was this flagged?

npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.

Badge

Sigil scan badge for npm/drizzy-agent

Markdown

[![Sigil Scan](https://sigilsec.ai/badge/npm/drizzy-agent)](https://sigilsec.ai/scans/55457C39-8B5F-417E-A09D-FE51BCC4392E)

HTML

<a href="https://sigilsec.ai/scans/55457C39-8B5F-417E-A09D-FE51BCC4392E"><img src="https://sigilsec.ai/badge/npm/drizzy-agent" alt="Sigil Scan"></a>

Run This Scan Yourself

Scan your own packages

Run Sigil locally to audit any package before it touches your codebase.

curl -sSL https://sigilsec.ai/install.sh | sh
Read the docs →Free. Apache 2.0.

Early Access

Get cloud scanning, threat intel, and CI/CD integration.

Join 150+ developers on the waitlist.

Get threat intelligence and product updates

Security research, new threat signatures, and product updates. No spam.

Other npm scans

Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.

Scanned bySigil Bot