# MAL-2026-6198: Malicious code in new-ecro-1 (npm)


- **Type:** Malicious package
- **Package:** `new-ecro-1` (npm)
- **Published:** 19 Jun 2026
- **Also known as:** GHSA-j799-pq44-wq6g

## What is MAL-2026-6198?

MAL-2026-6198 is a malicious package in new-ecro-1, published on 19 Jun 2026. 

### Official description

Package `new-ecro-1` impersonates the legitimate `big.js` library by shipping its source verbatim (banner, license, and homepage pointing at MikeMcl/big.js). Inside the load-time IIFE in both `big.js` and `big.mjs` at line 606, an injected block silently executes `const doc = require("parket-slot"); doc.from_str().then(e => {}).catch(e => {})`, wrapped in a try/catch that swallows all errors. The `parket-slot` package is not declared in this manifest's `dependencies` (which instead lists `new-solt-1`), so the require resolves to whatever loader-controlled package happens to be present in the surrounding install tree, executing its `from_str()` on import. The combination of name-impersonation, undeclared cross-package require, and silent error suppression is a loader stub for attacker-controlled code that runs the moment any consumer imports this module.

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.

## What should I do about MAL-2026-6198?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6198 is a malicious package: new-ecro-1 (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6198/ (Markdown: https://insights.sbomify.com/MAL-2026-6198/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6198

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6198/
Summaries are generated and may contain mistakes; the official description above is the record.