nodejs-npm-tokens-leak-march-2016: npm security updates v2.15.1 and v3.8.3

Published Mar 31, 2016
·
Updated

Affected Software

1 affected component
npm npm=2.15.1, =3.8.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.15.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.8.3

Event History

Mar 31, 2016
Advisory Published
via Node.js·10:41 AM
Data Sourced
via Node.js·10:41 AM
Description

Frequently Asked Questions

1

Which npm releases address this issue?

The security updates are npm v2.15.1 and npm v3.8.3.

2

When was this security update published?

It was published on 2016-03-31.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203