Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

NodeJS

The mysterious supply chain concern of string-width-cjs npm package

This story starts when Sébastien Lorber, maintainer of Docusaurus, the React-based open-source documentation project, notices a Pull Request change to the package manifest. Here’s the change proposed to the popular cliui npm package: Specifically, drawing our attention to the npm dependencies change that use an unfamiliar syntax: Most developers would expect to see a semver version range in the value of a package or perhaps a Git or file-based URL.

How to prevent log injection vulnerability in JavaScript and Node.js applications

In many standard enterprise applications, consistent logging serves a multitude of purposes. It helps businesses identify and rectify errors, provides valuable analytical insights, and lets you test new solutions. However, this also makes log injections one of the most common ways hackers can hijack or even gain access to sensitive user information.

A Developer's Tutorial to Using NPM Audit for Dependency Scanning

Many developers overlook the risks lurking in third-party packages. Every package you add could harbor vulnerabilities, potentially exposing sensitive user data and granting unauthorized access to your systems. It can lead to severe consequences, including data breaches, system compromises, reputation damage, and disruption of your services. With 80% of projects using at least one vulnerable package – it’s a crucial issue.