Malicious code in css-import-order (npm)

---

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (a190c01197be10bae5104dd08b8cb119ff1460eaa0c816bc0eb74da8a4b88ae4)

package.json declares the package's own name css-import-order as both a dependency and devDependency pointing at http://pack.nppacks.com/npm/css-import-order — a non-registry, plain-HTTP, unpinned URL under a domain unrelated to the npm publisher. On npm install, npm resolves and unpacks whatever tarball that host returns, executing any lifecycle scripts it contains. Because the source is not the npm registry, there is no integrity or version pinning, and the plain-HTTP transport additionally allows on-path substitution of the served bytes. The shipped index.js is a small benign transformer and carries a header comment reading This package use for Security Research Testing Purpose., but the harmful vector is the install-time resolution to attacker-mutable content at pack.nppacks.com, not the local module code.

Source: ghsa-malware (6c2915b485aa515505c532c5c5f456f1129ddf07ef25e014b7dae81bb15357f6)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.