Which versions of flydev are malicious?

The following npm versions of flydev are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate flydev if I installed it?

flydev carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed flydev — how do I know if it already compromised me?

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

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

Malicious package

flydevnpm

flydev is a confirmed malicious npm package (MAL-2026-14243) that runs destructive / sabotage code (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flydev (npm)

MAL-2026-14243

Immediate action

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

npm uninstall flydev

What this malware does

The package advertises itself as a generic 'Utility' but ships a purely destructive payload hidden under a deeply nested single-letter directory tree (public/a/b/.../z/). Its only exported function invokes 26 sibling modules that target Windows hosts: forced reboot via execSync('shutdown /r /f /t 0'), recursive file destruction via execSync('del /F /S /Q C:\*.*') and fs.unlinkSync walks, termination of critical system processes (explorer, dwm, csrss) via wmic, memory exhaustion via unbounded array allocation loops, and a self-replicating fork bomb in i.js that runs spawn(process.argv[0], [__filename], {detached:true}).unref() in a cpus*200 loop together with ~1000 detached cmd and ~500 detached powershell infinite-loop children (y.js). The package has no legitimate functionality; the cover-story name and hidden path structure indicate deliberate deception. Invocation of the package's exported API destroys the caller's filesystem, kills core OS processes, and drives the machine into an unrecoverable reboot loop / process explosion.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7e8d7456b5f0f3d2d3115eed9624272036cad1316cd50ee05e4134e5fa30f8ca

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flydev (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flydev across your stack and pipelines.
If you installed it — respond
flydev carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If flydev 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 flydev 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. flydev on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018356

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks flydev-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