Which versions of get-package-lint are malicious?

The following npm versions of get-package-lint are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate get-package-lint if I installed it?

get-package-lint 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 get-package-lint — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for get-package-lint (version 0.1.0).

Malicious package

get-package-lintnpm

Advisory published May 22, 2026Updated May 26, 2026

get-package-lint is a confirmed malicious npm package (MAL-2026-4572) that opens a backdoor for remote access (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in get-package-lint (npm)

MAL-2026-4572

Immediate action

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

npm uninstall get-package-lint

What this malware does

Package name typosquats the popular get-package-type and reuses its README/exports verbatim, but adds "postinstall": "node utils.cjs" in package.json. utils.cjs is a 263 KB obfuscator.io-protected blob (string-array rotation with anti-debug debugger loops, RegExp toString fingerprint, and Function('return this') sandbox checks) that on npm install: (1) decodes a hardcoded base64+XOR-obfuscated URL and bearer token (HF_TOKEN), (2) HTTPS-GETs a platform-specific binary (linux-x64 / darwin-arm64 / win32-x64 selected via DOWNLOAD_MAP), (3) writes it under the user's local data directory, chmod 0755 on POSIX, and spawns it detached, (4) installs OS-level persistence: on Windows via reg add HKCU\...\CurrentVersion\Run, on macOS via a LaunchAgent plist under ~/Library/LaunchAgents, on Linux via a systemd user unit at ~/.config/systemd/user/<unit>.service followed by systemctl --user daemon-reload && enable && start. The script also self-detaches by re-spawning itself with a child argv via {detached:true, stdio:'ignore'} and calling process.exit(0) so npm sees success while the dropper continues asynchronously. The fetched bytes are opaque, unverified (no hash/signature), and the source domain is not the package's publisher. This is an unambiguous binary-runner-dropper plus backdoor persistence triggered on every install.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

383f22ab2e1e8bbb44a44fa3828710f476947837d0b38aa9266eafcbf9959261

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for get-package-lint (version 0.1.0).
If you installed it — respond
get-package-lint 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 get-package-lint 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. get-package-lint on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004161

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks get-package-lint-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

Explore

All malware advisories How O3 detects malware Vulnerability database