From owner-freebsd-security@FreeBSD.ORG  Mon Mar 16 19:57:14 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D0F77556
 for <freebsd-security@freebsd.org>; Mon, 16 Mar 2015 19:57:14 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by mx1.freebsd.org (Postfix) with ESMTP id B7D7BA85
 for <freebsd-security@freebsd.org>; Mon, 16 Mar 2015 19:57:14 +0000 (UTC)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t2GJv8FR064104
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-security@freebsd.org>; Mon, 16 Mar 2015 12:57:08 -0700 (PDT)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Message-ID: <55073593.50108@rawbw.com>
Date: Mon, 16 Mar 2015 12:57:07 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Subject: npm doesn't check package signatures, should www/npm print security
 alert?
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2015 19:57:14 -0000

www/npm downloads and installs packages without having signature 
checking in place.
There is the discussion about package security 
https://github.com/node-forward/discussions/issues/29 , but actual 
checking isn't currently done.

Additionally, npm allows direct downloads of GitHub projects without any 
authenticity checking or maintainer review, see  documentation 
https://docs.npmjs.com/cli/install . Non-explicit syntax 'npm install 
githubname/reponame' can also be easily confused with the official 
package name. Random GitHub projects can contain code without any 
guarantees.

I think there is the risk that some malicious JavaScript code can be 
injected through the MITM attack, and server side JavaScript is a fully 
functional language.

Shouldn't www/npm at least print a security alert about this? It 
probably shouldn't be used on production systems until package 
authentication is in place.

Yuri