Which versions of new-ecro-helper are malicious?

The following npm versions of new-ecro-helper are flagged malicious: 5.8.0. Treat any of these as compromised.

How do I remediate new-ecro-helper if I installed it?

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

If new-ecro-helper 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 new-ecro-helper part of a known attack campaign?

Yes — new-ecro-helper is associated with the GHSA-85xv-pw78-4hqp, IN-MAL-2026-007423 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 new-ecro-helper 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 new-ecro-helper (version 5.8.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-ecro-helper across your stack and pipelines.

Malicious package

new-ecro-helpernpm

Malicious code in new-ecro-helper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6283

Immediate action

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

npm uninstall new-ecro-helper

What this malware does

The package publishes verbatim big.js v7.0.1 source (including the upstream copyright header, README, repository URL pointing to MikeMcl/big.js, and the upstream author's email) under the unrelated name new-ecro-helper. The main entry (big.js / big.mjs) has an injected loader block that runs on every require('new-ecro-helper'): try { const doc = require("new-helper"); doc.from_str().then(...).catch(...) } catch (error) { }. The dependency new-helper is declared as ^5.8.1 in package.json, so the semver caret admits any current or future 5.x.y version of that sibling package as the actual delivered payload. All errors from both the require and the invocation are swallowed by empty catch handlers, hiding the activity from the consuming application. The big.js code itself is unmodified and serves only as a cover library to disguise the loader. The net effect on installers: npm install new-ecro-helper pulls new-helper into the dependency tree, and any consumer that requires the package immediately and silently executes code in that sibling package.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

5.8.0

Indicators of compromise (SHA-256)

b45cdcd40f43adb9955aa6a4be1c14e4b35bea9595514d5d96151e1858b755e1

f0826d146dbc513ac14f403eaa9ba65dffbd04da52c55ff1840ad153dab96e87

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 new-ecro-helper (version 5.8.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-ecro-helper across your stack and pipelines.
If you installed it — respond
Remove new-ecro-helper 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 new-ecro-helper 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 new-ecro-helper 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. new-ecro-helper on npm has been identified as a malicious package (version 5.8.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-85xv-pw78-4hqpIN-MAL-2026-007423

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks new-ecro-helper-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