Which versions of testpackage83 are malicious?

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

How do I remediate testpackage83 if I installed it?

Remove testpackage83 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 activity or persistence.

I already installed testpackage83 — how do I know if it already compromised me?

If testpackage83 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is testpackage83 part of a known attack campaign?

Yes — testpackage83 is associated with the IN-MAL-2026-022781 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 testpackage83 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testpackage83 (version 1.0.0).

Malicious package

testpackage83npm

Advisory published Nov 14, 2026Updated Nov 14, 2026

testpackage83 is a confirmed malicious npm package (MAL-2026-19938) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testpackage83 (npm)

MAL-2026-19938

Immediate action

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

npm uninstall testpackage83

What this malware does

The package's postinstall script downloads an executable from http://185.212.128.180/chromedriver.bat, writes it to ~/.celest/bin/chrome (or chrome.exe), sets it executable, and later launches it through puppeteer-core. The source is a bare IPv4 address over plain HTTP with no hash, signature, or version pinning, and the URL path is a Windows.bat named 'chromedriver' while the package frames the artifact as a patched Chromium. The same download-and-execute path is also reached from src/browser.js, which calls download() followed by puppeteer.launch({ executablePath }) on first library use, so require()/import of the package will fetch and run the binary even when the postinstall step is skipped via CELEST_SKIP_DOWNLOAD. The destination host is not associated with any legitimate Chromium publisher, and the operator of that host fully controls the bytes that are executed on the installer's machine.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

000cea12be23bd792df9085f773c94b79ee13ae70b5154f7d619847bf1b3f0d7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for testpackage83 (version 1.0.0).
If you installed it — respond
Remove testpackage83 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 activity or persistence.
Did it already run?
If testpackage83 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. testpackage83 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-022781

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks testpackage83-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database