NPM安装正在窃取你的密码——我构建了一个工具来捕获它。
NPM install is stealing your passwords – I built a tool to catch it

原始链接: https://westbayberry.com/product

## 依赖守护者:保护您的供应链 最近的供应链攻击(Chalk/Debug、Shai-Hulud、tj-actions)表明未经审查的依赖更新存在风险,即使没有已知的CVE。**依赖守护者**为您的CI/CD管道提供一个免费、自动的“入口闸”,以减轻这些风险。 它使用**26种行为检测器**分析每个包的更改,以识别恶意模式(如凭证窃取或网络数据泄露),在代码合并*之前*。每个更新都会收到一个风险评分和一个“通过/警告/阻止”的判定结果,并直接发布为PR评论。 主要功能包括:**可配置策略**(阈值、白名单)、**详细审计跟踪**以符合合规性要求,以及与流行的CI工具(GitHub Actions、GitLab CI等)的无缝集成。 依赖守护者具有高精度(99.95%的精确度),并优先考虑隐私——仅扫描npm包,并且提供自托管选项。它旨在赋予开发团队对其依赖项的控制权和信心,防止零日漏洞,并确保安全的软件供应链。

一位安全研究员ComCat发现,恶意npm包可以在应用程序启动*之前*窃取凭据,方法是利用`npm install`自动执行包脚本的功能。现有的安全工具,如Snyk和Dependabot,依赖于已知的漏洞数据库(CVE),因此会错过新型攻击。 为了解决这个问题,ComCat构建了**Dependency Guardian**,一个行为分析引擎,它可以扫描包代码中的恶意模式——包括凭据窃取和隐藏的“定时炸弹”——精度高达99.95%。它成功识别了绕过现有安全措施的威胁,例如最近的Chalk/Debug劫持事件。 Dependency Guardian利用26个检测器和53个放大器进行近3000次测试,直接分析代码,而不是依赖漏洞报告。 这篇文章引发了关于npm/Node为何没有实施类似的安全措施,以及它与Socket.dev等现有解决方案的比较的讨论。
相关文章

原文

Behavioral Supply Chain Intelligence

Get visibility into dependency behavior in your CI pipeline. Every package change gets a risk score and behavioral report — flag suspicious packages for review, auto-approve the rest. Configurable thresholds, allowlists, and a full audit trail for compliance.

No credit card required. Free forever.

2.6B Weekly downloads affected in the Chalk / Debug compromise.
500+ Packages infected by the Shai-Hulud npm worm.
23K Repositories impacted in the tj-actions supply chain incident.

Why You Need an Intake Gate

In 2025, these unreviewed dependency updates hit production.

None had a CVE. No intake process caught them. They merged through standard PR workflows.

2.6B chalk + debug hijack Weekly downloads compromised

500+ Shai-Hulud worm Packages infected in 24 hours

2,349 S1ngularity campaign Credentials stolen via install scripts

23K tj-actions breach Repos exposed, led to Coinbase breach

Without intake control
  • Dependencies merge unreviewed
  • CVE tools miss zero-day attacks
  • No policy enforcement on upgrades
  • No audit trail for compliance
With Dependency Guardian
  • Every upgrade gets a verdict before merge
  • Behavioral analysis catches new attacks
  • Configurable pass/warn/block thresholds
  • Full scan history and audit trail
Policy enforcement

Set thresholds, allowlist trusted packages, choose warn vs. block per repository. Your governance rules, automated.

Approval workflow

Every lockfile change gets a verdict posted as a PR comment. Review flagged packages before they merge.

5-minute CI setup

One YAML file or npm i -g @westbayberry/dg. Works with GitHub Actions, GitLab CI, Jenkins, and more.

Compliance-ready audit trail

Every scan logged with verdicts, risk scores, and findings. Built for teams that need to prove what was reviewed.

Detection accuracy validated against 11,000+ real packages (99.95% precision, 99.7% F1): See benchmarks →

How it works

From dependency change to approved merge in four steps.

Step 01

Pull Request

A developer opens a PR that adds or updates npm packages in your lockfile.

package-lock.json
Step 02

Scan for Attacks

26 behavioral detectors analyze every file in each package for malicious code patterns.

26 detectors
Step 03

Pass / Warn / Block

A risk score determines the verdict — safe to merge, review needed, or blocked outright.

risk score
Step 04

Ship Safe

Merge with confidence knowing every dependency change was analyzed before reaching main.

merge ready

❯_ GITHUB ACTIONS

PR #247 bump lodash 4.17.20 → 4.17.21 Scanning 3 changed packages... Running 26 detectors across 847 files PASS — safe to merge

❯_ CLI

$ dg scan Discovering package changes... Scanning 3 packages (git-diff)...   Dependency Guardian Score: 0 PASS 3 packages scanned, 0 flagged

In your pull request

Every dependency change gets a verdict posted directly in the PR. Review, approve, or block before merge.

Ship with confidence. Every dependency upgrade is reviewed, scored, and logged before it reaches main.

Built for dependency governance

Six capabilities that turn dependency updates into a controlled process.

CI enforcement on every PR

Runs automatically when package-lock.json changes. One YAML file. Every dependency upgrade goes through your intake gate before it can merge.

Configurable policy engine

Set risk thresholds per repository. Allowlist trusted packages. Choose between warn and block modes. Your governance rules, enforced automatically.

Pass / Warn / Block verdicts

Every PR gets a risk score and a clear verdict. Block mode prevents merging. Warn mode flags for human review. Your team stays in control.

Audit trail and scan history

Every scan is logged with verdicts, risk scores, and findings. Track who approved what, when. Built for compliance reviews and security audits.

Behavioral analysis engine

26 detectors analyze what packages actually do — install scripts, network calls, credential access, obfuscation. Catches zero-day attacks that CVE databases miss.

Your source code stays private

Only npm packages are scanned. Your application code is never uploaded. Self-hosted option available for enterprise environments.

What powers the verdicts

26 behavioral detectors analyze what packages actually do — the engine behind every pass, warn, and block decision.

Install Scripts Child Process Network Exfiltration Obfuscation Diff Risk Fresh Publish Maintainer Change Sensitive Paths Binary Addons Filesystem Persistence CI Secret Access Suspicious API GitHub Reputation Source Mismatch Purpose Mismatch Typosquat Root Scripts Behavior Drift Token Theft Worm Behavior Preinstall Timing Legitimate API Exfil Bun Runtime Evasion Dependency Confusion Browser Phishing Empty Package

Works everywhere you build

GitHub Actions, GitLab CI, Jenkins, Bitbucket, CircleCI, or your terminal.

联系我们 contact @ memedata.com