Which versions of ngsw-config are malicious?

The following npm versions of ngsw-config are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ngsw-config if I installed it?

Remove ngsw-config from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ngsw-config — how do I know if it already compromised me?

If ngsw-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is ngsw-config part of a known attack campaign?

Yes — ngsw-config is associated with the IN-MAL-2026-018358 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ngsw-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ngsw-config (version 1.0.0).

Malicious package

ngsw-confignpm

ngsw-config is a confirmed malicious npm package (MAL-2026-14251) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ngsw-config (npm)

MAL-2026-14251

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ngsw-config

What this malware does

The package's postinstall lifecycle script collects installer host identifiers (hostname, platform, architecture, Node version, package/lifecycle name, timestamp) and POSTs them as JSON to the hardcoded endpoint https://wxc97jnc.instances.poc.jchunt.top/ngsw-config on npm install, with no consent, documentation, or opt-out. The package name shadows Angular's legitimate ngsw-config tooling, matching a dependency-confusion canary pattern in which internal build systems that misresolve the name automatically report identifying metadata to the operator of the poc.jchunt.top host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8b427c73f093ad680033b2779c43c1c96186a71055aaff3cf44befd18c2cecbd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ngsw-config (version 1.0.0).
If you installed it — respond
Remove ngsw-config from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ngsw-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ngsw-config on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018358

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ngsw-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database