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?

Remove @qlab/component-intelligence from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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.

Can O3 Security detect @qlab/component-intelligence in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @qlab/component-intelligence and packages like it before any post-install script runs.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection