MAL-2026-18285 Malicious code in @postex/common (npm)
Malicious package
Published
MAL-2026-18285 is a malicious package: @postex/common (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-18285/ (Markdown: https://insights.sbomify.com/MAL-2026-18285/index.md)
- Package
- @postex/common
- Registry
- npm
What is MAL-2026-18285?
MAL-2026-18285 is a malicious package in @postex/common, published on 25 Oct 2026.
Official description
@postex/[email protected] ships an inert index.js (module.exports = {}) and declares a single dependency
ltidisafe whose value is a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.5.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes that URL returns, installs the resulting package, and executes any lifecycle scripts it contains, with no registry-mediated integrity, signature, or version pinning. The host (a user-controlled Google Cloud Storage bucket) is unrelated to any npm scope or published repository for this package, and the content served there can change at any time without any change to this manifest. The implausibly high version (99.9.1) combined with a hollow stub and an off-registry source is consistent with a dependency-confusion / smuggling lure whose only install-time effect is resolving to attacker-controlled code.What should I do about MAL-2026-18285?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.