Which versions of pinochiomathm are malicious?

The following npm versions of pinochiomathm are flagged malicious: 2.3.2, 2.3.3, 2.3.4, 2.3.5. Treat any of these as compromised.

How do I remediate pinochiomathm if I installed it?

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

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

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

Yes — pinochiomathm is associated with the IN-MAL-2026-019951, IN-MAL-2026-019952, IN-MAL-2026-019950, IN-MAL-2026-019949 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 pinochiomathm 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 pinochiomathm (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pinochiomathm across your stack and pipelines.

Malicious package

pinochiomathmnpm

pinochiomathm is a confirmed malicious npm package (MAL-2026-16123) that typosquats a legitimate package to trick installs (malicious versions 2.3.2, 2.3.3, 2.3.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pinochiomathm (npm)

MAL-2026-16123

Immediate action

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

npm uninstall pinochiomathm

What this malware does

The package impersonates picomatch (name 'pinochiomathm', description copied from picomatch, homepage pointing at github.com/micromatch/picomach). On require, lib/pinochiomathm.js reads lib/parse.ts.map, base64-decodes it into parsetmp.js, and requires it. The decoded module performs an HTTP GET to https://www.jsonkeeper.com/b/V6NBX with a decoded 'x-secret-key' header, AES-256-CBC-decrypts the response using a hardcoded password, and passes the plaintext to eval(). A second disguised file lib/init.ts.map contains an additional base64-wrapped payload of the same shape. After execution the loader unlinks lib/parse.ts.map, parsetmp.js, lib/init.ts.map and config.js to remove the staged payload from disk. The result is arbitrary remote code execution in the installer's Node process, controlled by whoever edits the jsonkeeper paste, with anti-analysis evasion via sourcemap-filename disguise, base64+AES wrapping, and post-execution cleanup.

Malicious versions

4 flagged

2.3.22.3.32.3.42.3.5

Indicators of compromise (SHA-256)

135c673bb3925502b10f92d9819d956004ade25faa9c358f6d3fb2c67cd6114e

e904cc2e2811b5386aaa2fe68f76462ea4f20c5bb815948fb887ea35ddaadbe2

34bc05f26caa61320e470e7dffe7120af1e4e56e8f20a2bc7ea4751cdbe83068

8bad340e7ac756b19a8e0ed7021f7378855b1b4e5c7f7091636d34f291baa41a

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 pinochiomathm (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pinochiomathm across your stack and pipelines.
If you installed it — respond
pinochiomathm is a typosquat — you almost certainly intended a legitimately-named package. Remove pinochiomathm, 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 pinochiomathm 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 pinochiomathm 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. pinochiomathm on npm has been identified as a malicious package (versions 2.3.2, 2.3.3, 2.3.4, 2.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019951IN-MAL-2026-019952IN-MAL-2026-019950IN-MAL-2026-019949

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pinochiomathm-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