Which versions of config-helper-kit are malicious?

The following npm versions of config-helper-kit are flagged malicious: 1.3.2. Treat any of these as compromised.

How do I remediate config-helper-kit if I installed it?

Remove config-helper-kit 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 config-helper-kit — how do I know if it already compromised me?

If config-helper-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is config-helper-kit part of a known attack campaign?

Yes — config-helper-kit is associated with the IN-MAL-2026-018335 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 config-helper-kit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for config-helper-kit (version 1.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging config-helper-kit across your stack and pipelines.

Malicious package

config-helper-kitnpm

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

Malicious code in config-helper-kit (npm)

MAL-2026-14235

Immediate action

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

npm uninstall config-helper-kit

What this malware does

[email protected] exposes a default function getPlugin that issues an HTTPS request to a hardcoded bare-IP host (https://31.97.137.157:45000/icons/109) and passes the returned data.credits field into new Function('require','module',...), executing attacker-controlled JavaScript in the caller's Node.js process with require and module injected. The file also ships an unused helper referencing legitimate CDN hostnames (cloudflare, fastly, akamai, cdnjs) and uses icon/logo/credits naming, while the actual network target is a bare IP unrelated to any CDN. The package's README advertises it as a TypeScript/Tailwind config helper; the remote-code-fetch-and-execute behavior is undocumented and unrelated to that purpose. Any consumer that imports and invokes the default export grants the operator of 31.97.137.157:45000 arbitrary code execution on the installer's host.

Malicious versions

1 flagged

1.3.2

Indicators of compromise (SHA-256)

1033a9895c7d1a1b4d2c3f671caa239bd40f3985ab71d096fd25fbb7c977ef71

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for config-helper-kit (version 1.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging config-helper-kit across your stack and pipelines.
If you installed it — respond
Remove config-helper-kit 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 config-helper-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks config-helper-kit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-018335

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks config-helper-kit-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