Which versions of @dsft/ft-element are malicious?

The following npm versions of @dsft/ft-element are flagged malicious: 2.5.9. Treat any of these as compromised.

How do I remediate @dsft/ft-element if I installed it?

@dsft/ft-element 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 @dsft/ft-element — how do I know if it already compromised me?

If @dsft/ft-element 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 @dsft/ft-element part of a known attack campaign?

Yes — @dsft/ft-element is associated with the IN-MAL-2026-006755, GHSA-5g88-35hm-8xr7 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 @dsft/ft-element 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 @dsft/ft-element (version 2.5.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @dsft/ft-element across your stack and pipelines.

Malicious package

@dsft/ft-elementnpm

@dsft/ft-element is a confirmed malicious npm package (MAL-2026-5889) that opens a backdoor for remote access (malicious version 2.5.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dsft/ft-element (npm)

MAL-2026-5889

Immediate action

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

npm uninstall @dsft/ft-element

What this malware does

On npm install, the package's preinstall hook (preinstall: node index.js in package.json) executes index.js, which reads process.env.INIT_CWD, derives the installing project's directory name via path.basename(), and POSTs a JSON beacon {pkg, timestamp, transport, project} to a hardcoded callback URL https://deepbounty.dd06-dev.fr/cb/e51c2215-3fa8-48f1-ad64-1cf792e0cccc. The package is published under the @dsft scope and self-describes as a dependency-confusion PoC (description: Security PoC for Bug Bounty; index.js comment: Harmless dependency confusion PoC). Any build pipeline that expects a private @dsft/ft-element package and resolves to this public version will silently leak the project's directory name — which typically equals the private package/repo name — to a third-party endpoint, confirming a successful dependency-confusion takeover target. Installers receive no disclosure or consent. Although the author frames this as harmless research, the mechanism (unconditional install-time beacon containing host-identifying context to an attacker-controlled URL) is a supply-chain attack against any installer the scope collision affects.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.5.9

Indicators of compromise (SHA-256)

7a7ba80413e901c3cf618c92bd61dc6942bf167fac46b0dc7c554a4a06f705c1

0fc27cb5231d8e595b68443972813ec37c791f1beaf441561cf1e1a18b135cbb

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

Campaign

IN-MAL-2026-006755GHSA-5g88-35hm-8xr7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @dsft/ft-element-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