Which versions of constructor-blocks-landings are malicious?

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

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

Remove constructor-blocks-landings 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-landings — how do I know if it already compromised me?

If constructor-blocks-landings 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-landings part of a known attack campaign?

Yes — constructor-blocks-landings is associated with the IN-MAL-2026-015105 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-landings 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-landings (version 35.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging constructor-blocks-landings across your stack and pipelines.

Malicious package

constructor-blocks-landingsnpm

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

Malicious code in constructor-blocks-landings (npm)

MAL-2026-12661

Immediate action

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

npm uninstall constructor-blocks-landings

What this malware does

On require() of the package's main entrypoint, index.js loads setup.js which selects an OS/architecture-specific asset and downloads a binary from a rotating list of hostnames assembled at runtime via string-splitting (e.g. ["oob-worker.cf101-adf.wo","rkers.de","v"].join("")), with a DNS-TXT fallback under dl.wel1.ru. The downloaded bytes are written to a temp directory under a disguised name (dotnet_diag_<rand>.exe on Windows,.cache_<rand> on Unix), chmodded 0755, and spawned detached via cmd.exe or /bin/sh -c "<path> &" with stdio ignored. Node built-ins are accessed through computed property names (os[k], fs['chmod'+'Sync'], require('child_'+'process')) to defeat static analysis. A secondary copy of the same primitives is bundled in lib/telemetry.js under a fake analytics/SDK shape. Hostname reassembly, disguised staged filenames, detached background execution, and a DNS covert channel are attacker-dropper shape, not telemetry.

Malicious versions

1 flagged

35.5.7

Indicators of compromise (SHA-256)

28cdac4c3410baaaa9054b53e7d5ed9260e8322d3164fc5e1670c2ac15efa98b

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-landings (version 35.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging constructor-blocks-landings across your stack and pipelines.
If you installed it — respond
Remove constructor-blocks-landings 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-landings 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-landings 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-landings on npm has been identified as a malicious package (version 35.5.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015105

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks constructor-blocks-landings-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