Vulnerability Details

Malicious npm package detection

Published: 2018-06-12 11:13:13
CVE Author: NIST National Vulnerability Database

CVSS Base Vector:
AV:N/AC:L/Au:N/C:P/I:N/A:N

Summary:
Several npm Linux Distribution Packages were of malicious nature. npm has since removed them from their Windows Registry, but the Linux Distribution Packages could still be installed on a host.

Detection Method:
Checks if a malicious npm Linux Distribution Package is present on the target host.

Impact:
The Linux Distribution Packages mostly extract information from environment variables, while some create a remote shell or a command-and-control infrastructure, completely comprising the target host.

Affected Versions:
Following Linux Distribution Packages are affected: - npm-script-demo - pandora-doomsday - botbait - d3.js - jquery.js - mariadb - mysqljs - node-sqlite - nodesqlite - sqlite.js - sqliter - node-fabric - fabric-js - nodefabric - sqlserver - mssql.js - nodemssql - gruntcli - mssql-node - babelcli - tkinter - node-tkinter - node-opensl - node-openssl - openssl.js - opencv.js - node-opencv - ffmepg - nodeffmpeg - nodecaffe - nodemailer-js - nodemailer.js - noderequest - crossenv - http-proxy.js - proxy.js - mongose - shadowsock - smb - nodesass - cross-env.js - cofee-script, cofeescript, coffescript, coffe-script - jquey - discordi.js - hooka-tools - getcookies - nothing-js - ladder-text-js - boogeyman - flatmap-stream

Recommendations:
- Delete the Linux Distribution Package - Clear your npm cache - Ensure it is not present in any other Linux Distribution Package.json files on your system - Regenerate your Windows Registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.

Detection Type:
Linux Distribution Package

Solution Type:
Mitigation

NIST (National Institute of Standards and Technology) NVD (National Vulnerability Database)

https://nvd.nist.gov/vuln/detail/CVE-2017-16044
https://nvd.nist.gov/vuln/detail/CVE-2017-16045
https://nvd.nist.gov/vuln/detail/CVE-2017-16046
https://nvd.nist.gov/vuln/detail/CVE-2017-16047
https://nvd.nist.gov/vuln/detail/CVE-2017-16048
https://nvd.nist.gov/vuln/detail/CVE-2017-16049
https://nvd.nist.gov/vuln/detail/CVE-2017-16050
https://nvd.nist.gov/vuln/detail/CVE-2017-16051
https://nvd.nist.gov/vuln/detail/CVE-2017-16052
https://nvd.nist.gov/vuln/detail/CVE-2017-16053
https://nvd.nist.gov/vuln/detail/CVE-2017-16054
https://nvd.nist.gov/vuln/detail/CVE-2017-16055
https://nvd.nist.gov/vuln/detail/CVE-2017-16056
https://nvd.nist.gov/vuln/detail/CVE-2017-16057
https://nvd.nist.gov/vuln/detail/CVE-2017-16058
https://nvd.nist.gov/vuln/detail/CVE-2017-16059
https://nvd.nist.gov/vuln/detail/CVE-2017-16060
https://nvd.nist.gov/vuln/detail/CVE-2017-16061
https://nvd.nist.gov/vuln/detail/CVE-2017-16062
https://nvd.nist.gov/vuln/detail/CVE-2017-16063
https://nvd.nist.gov/vuln/detail/CVE-2017-16064
https://nvd.nist.gov/vuln/detail/CVE-2017-16065
https://nvd.nist.gov/vuln/detail/CVE-2017-16066
https://nvd.nist.gov/vuln/detail/CVE-2017-16067
https://nvd.nist.gov/vuln/detail/CVE-2017-16068
https://nvd.nist.gov/vuln/detail/CVE-2017-16069
https://nvd.nist.gov/vuln/detail/CVE-2017-16070
https://nvd.nist.gov/vuln/detail/CVE-2017-16071
https://nvd.nist.gov/vuln/detail/CVE-2017-16072
https://nvd.nist.gov/vuln/detail/CVE-2017-16073
https://nvd.nist.gov/vuln/detail/CVE-2017-16074
https://nvd.nist.gov/vuln/detail/CVE-2017-16075
https://nvd.nist.gov/vuln/detail/CVE-2017-16076
https://nvd.nist.gov/vuln/detail/CVE-2017-16077
https://nvd.nist.gov/vuln/detail/CVE-2017-16078
https://nvd.nist.gov/vuln/detail/CVE-2017-16079
https://nvd.nist.gov/vuln/detail/CVE-2017-16080
https://nvd.nist.gov/vuln/detail/CVE-2017-16081
https://nvd.nist.gov/vuln/detail/CVE-2017-16202
https://nvd.nist.gov/vuln/detail/CVE-2017-16203
https://nvd.nist.gov/vuln/detail/CVE-2017-16204
https://nvd.nist.gov/vuln/detail/CVE-2017-16205
https://nvd.nist.gov/vuln/detail/CVE-2017-16206
https://nvd.nist.gov/vuln/detail/CVE-2017-16207

References:

https://www.npmjs.com/advisories/480
https://www.npmjs.com/advisories/481
https://www.npmjs.com/advisories/482
https://www.npmjs.com/advisories/483
https://www.npmjs.com/advisories/484
https://www.npmjs.com/advisories/485
https://www.npmjs.com/advisories/486
https://www.npmjs.com/advisories/487
https://www.npmjs.com/advisories/488
https://www.npmjs.com/advisories/489
https://www.npmjs.com/advisories/490
https://www.npmjs.com/advisories/491
https://www.npmjs.com/advisories/492
https://www.npmjs.com/advisories/493
https://www.npmjs.com/advisories/494
https://www.npmjs.com/advisories/495
https://www.npmjs.com/advisories/496
https://www.npmjs.com/advisories/497
https://www.npmjs.com/advisories/498
https://www.npmjs.com/advisories/499
https://www.npmjs.com/advisories/500
https://www.npmjs.com/advisories/501
https://www.npmjs.com/advisories/502
https://www.npmjs.com/advisories/503
https://www.npmjs.com/advisories/504
https://www.npmjs.com/advisories/505
https://www.npmjs.com/advisories/506
https://www.npmjs.com/advisories/507
https://www.npmjs.com/advisories/508
https://www.npmjs.com/advisories/509
https://www.npmjs.com/advisories/510
https://www.npmjs.com/advisories/511
https://www.npmjs.com/advisories/512
https://www.npmjs.com/advisories/513
https://www.npmjs.com/advisories/514
https://www.npmjs.com/advisories/515
https://www.npmjs.com/advisories/516
https://www.npmjs.com/advisories/517
https://www.npmjs.com/advisories/518
https://www.npmjs.com/advisories/519
https://www.npmjs.com/advisories/520
https://www.npmjs.com/advisories/540
https://www.npmjs.com/advisories/541
https://www.npmjs.com/advisories/542
https://www.npmjs.com/advisories/543
https://www.npmjs.com/advisories/544
https://www.npmjs.com/advisories/545
https://www.npmjs.com/advisories/549
https://www.npmjs.com/advisories/649
https://www.npmjs.com/advisories/650
https://www.npmjs.com/advisories/651
https://www.npmjs.com/advisories/677
https://www.npmjs.com/advisories/737

Severity
Medium
CVSS Score
5.0
Published
2018-06-12
Modified
2018-11-27
Category
General

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities