MAL-2026-10639 Malicious code in ogensec-sdk (npm)
Malicious package
Published
MAL-2026-10639 is a malicious package: ogensec-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-10639/ (Markdown: https://insights.sbomify.com/MAL-2026-10639/index.md)
- Package
- ogensec-sdk
- Registry
- npm
What is MAL-2026-10639?
MAL-2026-10639 is a malicious package in ogensec-sdk, published on 15 Jul 2026.
Official description
The package ships an Express middleware that, on each incoming request, POSTs {appId, endpoint} to a configured
${baseUrl} and interprets the response as a list of items containing a hotfix.code string. That string is wrapped as return (async ()=>{ <code> })(); and passed to Object.getPrototypeOf(async function(){}).constructor (AsyncFunction) with require, req, res parameters, then awaited. Any JavaScript returned by the configured server therefore runs inside the installer's Node process with full require access and access to the live request/response objects on every HTTP request served through the middleware. The feature is marketed only as 'Dynamic security hotfixes' and is not documented as arbitrary remote code execution. The entire shipped dist/ tree (index.js, bridge.js, client.js) is processed by javascript-obfuscator (rotated base64 string arrays, hex-named identifiers) as declared by the obfuscate/prepublishOnly scripts in package.json, and no source is published — concealing the remote-code-execution mechanism from developers reviewing the SDK. Any compromise, takeover, or on-path MITM of the configured backend converts every deployment using this middleware into a live RCE on production traffic; the maintainer of the backend also holds a persistent, undisclosed remote-execution channel into every installer.What should I do about MAL-2026-10639?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.