1-minute read
What a defender needs to know
An active campaign implicated 846 npm components in cross-platform native-malware delivery. Importing an affected package can start the chain even when npm lifecycle scripts are disabled.
The loader tries three Cloudflare Workers HTTPS hosts, then falls back to numbered DNS TXT records beneath wel1[.]ru. It reconstructs a platform-specific payload, writes it into a temporary path, and launches it detached. The analyzed Windows and macOS stages can add evasion and persistence, so deleting the dependency does not clear a host after execution.
Search Sonatype’s current sonatype-2026-005660 list across lockfiles, caches, mirrors, container layers, developer systems, and CI runners. The sources provide no fixed clean package version or build, so that live list supersedes static package-name and 35.x.y checks. Correlate matches with process ancestry, TXT lookups, Workers domains, persistence artifacts, and credential use. Confirm removed packages cannot return through direct or transitive resolution. For executed packages, follow Sonatype’s order: isolate, preserve and investigate evidence, eradicate or rebuild as appropriate, and rotate developer or build secrets from a clean machine only after remediation.
Once the native stage may have run, npm becomes the opening scene. The package name disappears from the lockfile faster than its host and account consequences do.