Which versions of fluterjs are malicious?

The following npm versions of fluterjs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate fluterjs if I installed it?

fluterjs 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 fluterjs — how do I know if it already compromised me?

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

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

Malicious package

fluterjsnpm

Malicious code in fluterjs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10532

Immediate action

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

npm uninstall fluterjs

What this malware does

The package's main and bin entry, server.js, starts an Express server bound to 0.0.0.0:10459 that exposes POST /ejecutar. The handler reads the JSON field comando and passes it directly to child_process.exec with no authentication, no origin check, and no command allowlist. When an operator runs fluter or npm start, any network-reachable caller (LAN, container network, or the public internet if the host is exposed) obtains arbitrary shell command execution on the host as the user who launched the tool. The package presents itself as a terminal helper, but the shipped behavior is a remote shell distributed as a feature — a backdoor by design.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bb8d561ceacd48c1883f6ec3151f5567240259b5ba54af3835fc0537f2f18933

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

Campaign

IN-MAL-2026-010386

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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