Which versions of type-plint are malicious?

The following npm versions of type-plint are flagged malicious: 3.3.7. Treat any of these as compromised.

How do I remediate type-plint if I installed it?

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

I already installed type-plint — how do I know if it already compromised me?

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

Yes — type-plint is associated with the IN-MAL-2026-009611, GHSA-8mhh-r4mc-2293 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 type-plint 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 type-plint (version 3.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging type-plint across your stack and pipelines.

Malicious package

type-plintnpm

Malicious code in type-plint (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10130

Immediate action

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

npm uninstall type-plint

What this malware does

The package advertises itself as a pino-style logger but its exported middleware spawns lib/caller.js as a detached Node child process. lib/caller.js performs an HTTP GET against a third-party mutable JSON-bin host (json.extendsclass.com/bin/26d6d7d075e1, with secondary jsonkeeper.com bins) and passes the returned string to new Function.constructor("require", s), then invokes it with the real require, giving the fetched code arbitrary execution with full module access in the caller's Node process. lib/const.js and lib/caller.js embed base64-encoded jsonkeeper.com bin URLs disguised as environment-variable defaults (e.g. DEV_API_KEY decodes to https://jsonkeeper.com/b/XRGF3), a standard evasion shape for staged remote-code loaders. The pino-like API surface and module.exports.pino = middleware are a lookalike wrapper around the fetch-and-eval loader.

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

3.3.7

Indicators of compromise (SHA-256)

37979cc60cff25e26406f3426f0dd7aeac12c13e55402c89f78228080cac0ad9

03a124b9fdf68baca03f8e109847668f7265163746492e8fb234cf1822a4464a

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

Campaign

IN-MAL-2026-009611GHSA-8mhh-r4mc-2293

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks type-plint-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