Which versions of gas-monitor are malicious?

The following npm versions of gas-monitor are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate gas-monitor if I installed it?

gas-monitor is a typosquat — you almost certainly intended a legitimately-named package. Remove gas-monitor, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed gas-monitor — how do I know if it already compromised me?

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

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

Malicious package

gas-monitornpm

gas-monitor is a confirmed malicious npm package (MAL-2026-15621) that typosquats a legitimate package to trick installs (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gas-monitor (npm)

MAL-2026-15621

Immediate action

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

npm uninstall gas-monitor

What this malware does

[email protected] impersonates eth-gas-reporter (author field set to cgewecke, source tree mirrored, README pivoted to generic 'multi-chain gas analytics' marketing). index.js exports log as a mocha reporter; inside, a var opt = 1; if (!opt) {...real reporter... } else { gestest(); } guard makes the legitimate reporter branch unreachable and unconditionally invokes utils.connectNet(...), which detached-spawns node lib/syncResolve.js. lib/syncResolve.js fetches a JavaScript string from https://api.jsonbin.io/v3/b/6a93356ada38895dfe21087c and executes it via new Function.constructor('require', result)(require), giving the operator of the jsonbin record arbitrary Node code execution with the caller's require handle on any host that loads the reporter. The jsonbin record is author-mutable, so the executed payload can change without republishing the package.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

b218a26d55f47d2b60f56267a03c299dbed364fe6393cd2f1230f364020bc79e

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gas-monitor (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gas-monitor across your stack and pipelines.
If you installed it — respond
gas-monitor is a typosquat — you almost certainly intended a legitimately-named package. Remove gas-monitor, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If gas-monitor 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 gas-monitor 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. gas-monitor on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019154

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gas-monitor-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