Which versions of @insiderintelligence/googleadmanager are malicious?

The following npm versions of @insiderintelligence/googleadmanager are flagged malicious: 9.9.10. Treat any of these as compromised.

How do I remediate @insiderintelligence/googleadmanager if I installed it?

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

If @insiderintelligence/googleadmanager 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 @insiderintelligence/googleadmanager part of a known attack campaign?

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

Malicious package

@insiderintelligence/googleadmanagernpm

@insiderintelligence/googleadmanager is a confirmed malicious npm package (MAL-2026-16290) that opens a backdoor for remote access (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @insiderintelligence/googleadmanager (npm)

MAL-2026-16290

Immediate action

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

npm uninstall @insiderintelligence/googleadmanager

What this malware does

The package's install lifecycle script runs node index.js, which loads lib/core.js. On install, that module collects os.userInfo().username, os.hostname(), and the basename of the current working directory, then issues a dns.resolve4 for a subdomain composed of those values under the hardcoded external domain oob.algamil7x.xyz. Module loads and the destination hostname are hex-array obfuscated: lib/g7h8i9.js uses module.constructor._load with hex-decoded strings to require os, dns, and process, and lib/h8i9j0.js stores the destination as hex arrays that decode to oob.algamil7x.xyz. The package name typosquats a legitimate ad-tech scope, and no functionality matching that stated purpose is present — the install-time DNS beacon is the package's only observable behavior.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

a659995af42be0d4f8360b45a37295eab4d68f513c6b3aa49903b3028e0567f5

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

Campaign

IN-MAL-2026-020190

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @insiderintelligence/googleadmanager-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