Which versions of typesens are malicious?

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

How do I remediate typesens if I installed it?

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

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

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

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

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

Malicious package

typesensnpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

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

Malicious code in typesens (npm)

MAL-2026-17565

Immediate action

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

npm uninstall typesens

What this malware does

package.json declares postinstall wscript.exe 4444.vbs, which runs automatically on npm install. The shipped 4444.vbs (~765 KB) contains a multi-layer decryption chain (AES S-box, ChaCha20-IETF, SHA-256 constants XOR-masked with 0x5A5A5A5A) over ~665 base64 chunks, decodes a payload to %TEMP% as a.dat file, drops a PowerShell loader, and invokes powershell.exe to perform process hollowing on Windows. Function names in the VBS are randomized (PlatformProbeLVI, DeviceCatalogUBYQ, EndpointRegistryRFX) and the CreateObject target is XOR-decoded at runtime; a cover-story header labels the file as a 'Verdant Signals Corp Device Telemetry Aggregator'. The advertised library surface — src/index.js is a trivial zod-based email-domain check with no network I/O, and the README claims 'No installation scripts' and describes a 'booking-eligibility' utility — is a decoy contradicting the package.json files entry that ships 4444.vbs and the postinstall hook that runs it. The typosquat-shaped name (typesens) reinforces the lure framing.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3ded39f31b2c2d4d73e0b576ab862c9ed90688153a43c359dae5b26854ad8738

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for typesens (version 1.0.0).
If you installed it — respond
typesens is a typosquat — you almost certainly intended a legitimately-named package. Remove typesens, 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 typesens 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. typesens 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-021028

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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