Which versions of type-elint are malicious?

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

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

type-elint establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

Yes — type-elint is associated with the IN-MAL-2026-009620 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-elint 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-elint (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-elint across your stack and pipelines.

Malicious package

type-elintnpm

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

MAL-2026-10137

Immediate action

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

npm uninstall type-elint

What this malware does

Package impersonates the pino logger (README is pino documentation, package name is a lookalike). The main export is a middleware factory that spawns lib/caller.js as a detached Node child process. caller.js retrieves JavaScript from hardcoded remote endpoints at https://json.extendsclass.com/bin/863e90480800 and https://jsonkeeper.com/b/XRGF3, then evaluates the response body using the Function constructor with require passed in scope, yielding arbitrary code execution in the consumer's environment under the endpoint owner's control. The destination URLs are base64-encoded and stored under a decoy DEV_API_KEY property (e.g., aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iL1hSR0Yz decodes to the jsonkeeper.com URL) to hide the C2/dead-drop from casual review. Mutable third-party paste services as the code source mean the delivered payload can change at any time without any package update.

Malicious versions

1 flagged

3.3.7

Indicators of compromise (SHA-256)

f29d6bfc122cb5792d95cfade56e62789f83366b30fc0d58a88a84113d89962c

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for type-elint (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-elint across your stack and pipelines.
If you installed it — respond
type-elint establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If type-elint 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-elint 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-elint 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-009620

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks type-elint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring