Which versions of constructor-blocks-common are malicious?

The following npm versions of constructor-blocks-common are flagged malicious: 35.5.6. Treat any of these as compromised.

How do I remediate constructor-blocks-common if I installed it?

Remove constructor-blocks-common from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed constructor-blocks-common — how do I know if it already compromised me?

If constructor-blocks-common was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is constructor-blocks-common part of a known attack campaign?

Yes — constructor-blocks-common is associated with the IN-MAL-2026-015109 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find constructor-blocks-common across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for constructor-blocks-common (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging constructor-blocks-common across your stack and pipelines.

Malicious package

constructor-blocks-commonnpm

constructor-blocks-common is a confirmed malicious npm package (MAL-2026-12660) that executes malicious code on install (malicious version 35.5.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in constructor-blocks-common (npm)

MAL-2026-12660

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall constructor-blocks-common

What this malware does

On require() of constructor-blocks-common, index.js loads helpers.js which invokes a bootstrap routine at module load. The routine reconstructs destination hostnames via Array.join string-splitting (e.g. 'oob-worker.cf102-baf.workers.dev', 'oob-worker.cf101-adf.workers.dev', 'oob-worker.cf99-9b3.workers.dev') plus a DNS-TXT fallback channel under *.dl.wel1.ru (linux_x64 host assembled from ['sd','k.d','l.wel1.','ru']), downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised filename (.cache<hex> or dotnet_diag_<hex>.exe), chmods 0755, and detaches it via spawn('/bin/sh', ['-c', filePath+' &']) or spawn('cmd',...). The fetched bytes are opaque, unpinned, and unrelated to the package's stated purpose of 'cross-module shared code'. A second copy of the dropper is bundled at lib/telemetry.js under an 'Analytics SDK' cover story (base64 chunk assembly, cp.spawn('/bin/sh',...), fs['chmod'+'Sync'] concatenated to evade static analysis). Cover-story comments ('Detached process to avoid blocking npm install', 'Clean up temporary files') accompany the exec paths. Installing or requiring this package results in remote code execution on the installer host.

Malicious versions

1 flagged

35.5.6

Indicators of compromise (SHA-256)

96701ff9ef8e8d7ed9b946a9cb3cc7efa18a6159a1729610892fb95dc6175c31

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for constructor-blocks-common (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging constructor-blocks-common across your stack and pipelines.
If you installed it — respond
Remove constructor-blocks-common from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If constructor-blocks-common was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks constructor-blocks-common before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. constructor-blocks-common on npm has been identified as a malicious package (version 35.5.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015109

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks constructor-blocks-common-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database