Which versions of adpanel-core are malicious?

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

How do I remediate adpanel-core if I installed it?

adpanel-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed adpanel-core — how do I know if it already compromised me?

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

Yes — adpanel-core is associated with the GHSA-jhrx-465c-725f, IN-MAL-2026-011210 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 adpanel-core 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 adpanel-core (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 adpanel-core across your stack and pipelines.

Malicious package

adpanel-corenpm

adpanel-core is a confirmed malicious npm package (MAL-2026-11453) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adpanel-core (npm)

MAL-2026-11453

Immediate action

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

npm uninstall adpanel-core

What this malware does

lib/report.js imports child_process, fs, https, and os, collects host identity via os.hostname() and os.userInfo(), reads local files via fs.readFileSync, executes commands via execSync, and POSTs the collected data over https.request to a hardcoded Zapier webhook at hooks.zapier.com. The destination is an attacker-controlled relay endpoint unrelated to any documented package purpose, and the data flow constitutes exfiltration of installer host identity, user info, and file contents.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b2ee116a6f3b542c8343e89be717fad00ec4605219c7d821f68aefe36610d4c7

1e99205329e726e32ed6884b52666e69e3327134c257dd1025464fed2fb461bf

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for adpanel-core (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 adpanel-core across your stack and pipelines.
If you installed it — respond
adpanel-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If adpanel-core 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 adpanel-core 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. adpanel-core 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

GHSA-jhrx-465c-725fIN-MAL-2026-011210

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks adpanel-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database