MAL-2026-18375 Malicious code in @dmangal/curse-dependent-ecto (npm)
Malicious package
Published
MAL-2026-18375 is a malicious package: @dmangal/curse-dependent-ecto (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-18375/ (Markdown: https://insights.sbomify.com/MAL-2026-18375/index.md)
- Package
- @dmangal/curse-dependent-ecto
- Registry
- npm
What is MAL-2026-18375?
MAL-2026-18375 is a malicious package in @dmangal/curse-dependent-ecto, published on 29 Oct 2026.
Official description
The package's binding.gyp contains a GYP command-expansion action that is executed automatically by node-gyp during
npm install. The embedded node -e script runs grep -rl 'HTB{' /workspace/ /root/ /tmp/ /opt/ /var/ /etc/ across installer-side paths, reads /tmp/scent-trail.jsonl and /workspace/repo/package.json, enumerates every key of process.env and concatenates each key=value pair, and POSTs each of these payloads (prefixed GREP:, FILE:, ALLENV:) to the hardcoded attacker endpoint webhook.site/89bd8fe7-328c-4e6d-970c-4d567b5a48a0. The binding.gyp has no accompanying native source files; its only purpose is to run the embedded exfiltration command. The implausibly high version string (99999.0.1) is consistent with a dependency-confusion lure. Installing this package in a developer workstation or CI environment causes CI secrets, API tokens, and environment-injected credentials, along with workspace file contents and any file containing the HTB{ marker, to be transmitted to an attacker-controlled host.What should I do about MAL-2026-18375?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.