Which versions of @qlab/component-intelligence are malicious?

The following npm versions of @qlab/component-intelligence are flagged malicious: 2.0.6. Treat any of these as compromised.

How do I remediate @qlab/component-intelligence if I installed it?

@qlab/component-intelligence 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 @qlab/component-intelligence — how do I know if it already compromised me?

If @qlab/component-intelligence 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 @qlab/component-intelligence part of a known attack campaign?

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

Malicious package

@qlab/component-intelligencenpm

Malicious code in @qlab/component-intelligence (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6184

Immediate action

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

npm uninstall @qlab/component-intelligence

What this malware does

package.json declares a preinstall hook ("preinstall": "node index.js") that fires automatically on npm install. index.js requires os, dns, https, querystring, and the package's own package.json, then collects the installer's hostname (os.hostname()), username (os.userInfo().username), home directory (os.homedir()), configured DNS servers (dns.getServers()), current working directory, and the full contents of package.json, and POSTs them via HTTPS to the hardcoded webhook https://eo1e4fhn1i67p8r.m.pipedream.net/. This is the canonical dependency-confusion / recon-beacon shape: host identifiers and internal package metadata leave the machine unconditionally at install time to an attacker-controlled endpoint, giving the attacker reconnaissance data on internal package names, corporate hostnames, and user identities to fuel follow-on supply-chain attacks.

Malicious versions

1 flagged

2.0.6

Indicators of compromise (SHA-256)

9ad49caeee790003270d74c5b17a58d0cef6f04d881efe83b0f6c7e11515e934

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

Campaign

IN-MAL-2026-007053

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @qlab/component-intelligence-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