Which versions of saas-f-lego-landings are malicious?

The following npm versions of saas-f-lego-landings are flagged malicious: 20.7.5. Treat any of these as compromised.

How do I remediate saas-f-lego-landings if I installed it?

saas-f-lego-landings establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed saas-f-lego-landings — how do I know if it already compromised me?

If saas-f-lego-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 saas-f-lego-landings part of a known attack campaign?

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

Malicious package

saas-f-lego-landingsnpm

saas-f-lego-landings is a confirmed malicious npm package (MAL-2026-12433) that opens a backdoor for remote access (malicious version 20.7.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in saas-f-lego-landings (npm)

MAL-2026-12433

Immediate action

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

npm uninstall saas-f-lego-landings

What this malware does

[email protected] executes a native binary dropper as a side effect of loading the package. index.js unconditionally requires./support.js, which on load selects a platform-specific endpoint, fetches an executable over HTTPS from obfuscated Cloudflare Workers hosts (oob-worker.cf10{0,1,2}-*.workers.dev) with a DNS TXT-record fallback to *.dl.well1.site, writes it to /tmp/.cache* on Unix or %TEMP%/dotnet_diag_.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. Destination hostnames are reconstructed at runtime via string-split.join() (e.g. ["oob","-worker.cf102-baf.workers.dev"].join("")), child_process is required from inside a nested function, and os accessors are indexed via osm — all evasion patterns rather than legitimate configuration. The tarball also ships lib/telemetry.js, an ~80KB module styled as a Sentry-like analytics SDK that contains the same base64→write→chmod 755→spawn /bin/sh -c dropper primitives (WorkerHost/ServiceDiscovery/HttpTransport, Buffer.from(chunks,"base64"), fs["chmod"+"Sync"](path, mode | parseInt("755",8))); it is not referenced by index.js but corroborates the observability-SDK cover story. Deceptive filenames (dotnet_diag_.exe,.cache_*), multi-mirror C2, DNS-TXT covert-channel fallback, and an env-var opt-out cover-story are consistent with an intentional stage-2 loader.

Malicious versions

1 flagged

20.7.5

Indicators of compromise (SHA-256)

0c96f58511420dcd956adbe21ee52dd1acae9956f5b562887a5c6659679fb52d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for saas-f-lego-landings (version 20.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging saas-f-lego-landings across your stack and pipelines.
If you installed it — respond
saas-f-lego-landings establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If saas-f-lego-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 saas-f-lego-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. saas-f-lego-landings on npm has been identified as a malicious package (version 20.7.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014721

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks saas-f-lego-landings-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database