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 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed get-package-lint — how do I know if it already compromised me?

If get-package-lint 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for get-package-lint (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging get-package-lint across your stack and pipelines.

Malicious package

get-package-lintnpm

Malicious code in get-package-lint (npm) Remove it immediately and rotate any exposed credentials.

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

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for get-package-lint (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging get-package-lint across your stack and pipelines.
If you installed it — respond
get-package-lint is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If get-package-lint 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 get-package-lint 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. 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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring