Which versions of helpersutils-dev-tools are malicious?

The following npm versions of helpersutils-dev-tools are flagged malicious: 1.0.11. Treat any of these as compromised.

How do I remediate helpersutils-dev-tools if I installed it?

helpersutils-dev-tools establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed helpersutils-dev-tools — how do I know if it already compromised me?

If helpersutils-dev-tools 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 helpersutils-dev-tools part of a known attack campaign?

Yes — helpersutils-dev-tools is associated with the IN-MAL-2026-020457 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 helpersutils-dev-tools 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 helpersutils-dev-tools (version 1.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging helpersutils-dev-tools across your stack and pipelines.

Malicious package

helpersutils-dev-toolsnpm

helpersutils-dev-tools is a confirmed malicious npm package (MAL-2026-16465) that opens a backdoor for remote access (malicious version 1.0.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in helpersutils-dev-tools (npm)

MAL-2026-16465

Immediate action

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

npm uninstall helpersutils-dev-tools

What this malware does

The package presents itself as 'Development utility helpers' but its main module executes an IIFE at require-time that issues an Image request to http://5.189.173.113:8899/csp-edu with document.domain appended as a query parameter. A sibling file bypass.js contains an equivalent beacon to http://5.189.173.113:8899/csp. Both destinations are a hardcoded bare IP over plain HTTP, unrelated to any advertised functionality, and receive host-context data (the consuming page's domain) whenever the module is loaded.

Malicious versions

1 flagged

1.0.11

Indicators of compromise (SHA-256)

85b7208dea3cf1742ac01332c17db9df968fd4a105fbccaf0b5388162b0f3673

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for helpersutils-dev-tools (version 1.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging helpersutils-dev-tools across your stack and pipelines.
If you installed it — respond
helpersutils-dev-tools establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If helpersutils-dev-tools 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 helpersutils-dev-tools 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. helpersutils-dev-tools on npm has been identified as a malicious package (version 1.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020457

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks helpersutils-dev-tools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database