MAL-2026-4688 Malicious code in tempo-shared-modules (npm)
Malicious package
Published
MAL-2026-4688 is a malicious package: tempo-shared-modules (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-4688/ (Markdown: https://insights.sbomify.com/MAL-2026-4688/index.md)
- Package
- tempo-shared-modules
- Registry
- npm
What is MAL-2026-4688?
MAL-2026-4688 is a malicious package in tempo-shared-modules, published on 25 May 2026.
Official description
On
npm install, the preinstall script poc.js collects host identity (hostname, username, OS/platform), network configuration (ipconfig / ip a / resolv.conf), git remote, the parent project's package.json, CI configuration files (.gitlab-ci.yml,.github/workflows, Jenkinsfile, azure-pipelines.yml), and bulk-scrapes process.env for any variable name matching TOKEN, AWS, AZURE, NPM, GITHUB, GITLAB, CI_, JENKINS, BUILD, or WALMART together with their values. The collected payload is POSTed over HTTPS to the hardcoded interactsh OAST endpoint d8a5d9pon5bugoc35cngp9hcregcqyezu.oast.me. The package is published at version 99.0.2 on the public npm registry under a name designed to be resolved by mistake instead of an internal @livingdesign/react private package — the canonical dependency-confusion shape. The package's own description self-labels it as a Walmart HackerOne PoC, but it is publicly installable and any non-Walmart installer that resolves it is harmed: their CI tokens, cloud credentials, and pipeline configuration are sent to a third-party OAST callback host. Any one of (preinstall env-credential scrape, hardcoded OAST exfil endpoint, dependency-confusion publication shape) is independently sufficient to block.What should I do about MAL-2026-4688?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.