The ability for attackers to leverage automatic install script execution in npm will finally come to an end when expected changes arrive from GitHub in July ... “Npm is not inventing a new doctrine.
GitHub will change npm's defaults so the install command no longer runs scripts automatically, disabling a feature commonly exploited by malicious packages such as the notorious Shai-Hulud worm ... Will this fix npm security issues? Unfortunately not.
Attackers planted an infostealer inside 36 npm packages linked to the Arweave ecosystem ... It activates the moment a developer installs an npm package ... All a victim had to do was run npm install ... Malware attacks keep hitting npm.
A new npm supply-chain attack has infected 36 packages with Rust-based infostealer malware called IronWorm ... The Rust-based malware self-propagates by using stolen credentials for publishing on npm; ...
gyp file to trigger execution during npm install, rather than relying on the preinstall or postinstall scripts that many security tools already monitor ... The article npm worm exploits hidden build trigger appeared first on ArabianPost.
Days after IBM and Red Hat announced a master security plan for open-source software, Red Hat suffers a major breach of its own. Here's what you can do about it ... .
TL;DRMicrosoft identified two compromised npm packages that secretly distributed malware capable of stealing cryptocurrency wallet credentials, keystrokes, screenshots, and other sensitive information.
Attackers have compromised Red Hat’s official @redhat-cloud-services namespace on npm, inserting credential-stealing malware into dozens of package releases used in cloud console development and software build pipelines.
Developers who pulled packages from Red Hat’s @redhat-cloud-services npm namespace over the weekend got a secret-stealing worm instead ... in software supply chain attacks targeting the npm ecosystem.