North Korea-Linked Malicious npm Packages Mimicking Rollup Polyfill Tooling

Technical Analysis

The malicious packages closely clone the description, README, and repository metadata of a legitimate Rollup polyfill package to evade cursory review and increase installation likelihood via typosquatting and brandjacking techniques. Once installed, the packages are reported to facilitate remote access capabilities and harvest developer secrets, likely including environment variables, SSH keys, npm/cloud tokens, and API credentials from local development environments or CI/CD pipelines. This aligns with known North Korean (Lazarus-affiliated) TTPs of targeting software supply chains to compromise downstream organizations and pivot into corporate networks. Because many AI agent frameworks, orchestration tools, and RAG pipelines are built on Node.js/JavaScript tooling and frequently pull dependencies transitively (including build tools like Rollup), a compromised developer machine or CI runner could leak LLM provider API keys, vector database credentials, or agent framework secrets, enabling downstream hijacking of agent infrastructure or unauthorized API usage at scale.

Affected Systems

Node.js/npm development environments and CI/CD pipelines that install 'rollup-packages-polyfill-core' or 'rollup-runtime-polyfill-core'; any project using Rollup-based build tooling that may inadvertently pull these typosquatted packages

Indicators of Compromise

• rollup-packages-polyfill-core (npm package name)
• rollup-runtime-polyfill-core (npm package name)

Remediation Steps

1. 1

   Audit installed dependencies

   Search package.json, package-lock.json, and node_modules across all projects and CI systems for 'rollup-packages-polyfill-core' or 'rollup-runtime-polyfill-core' and remove immediately if found.

2. 2

   Rotate exposed secrets

   Rotate all API keys, tokens, SSH keys, and credentials present on any system where the malicious packages were installed, including LLM/AI service API keys and cloud credentials used by agent pipelines.

3. 3

   Implement dependency allowlisting

   Use private npm registries or proxy configurations with strict allowlists to prevent installation of unverified or typosquatted packages.

4. 4

   Enable package integrity verification

   Enforce lockfile integrity checks, use tools like npm audit signatures, Socket.dev, or similar supply-chain security scanners in CI/CD pipelines.

5. 5

   Monitor for anomalous outbound connections

   Review network logs on developer workstations and build servers for unexpected remote access or data exfiltration traffic following recent package installs.